search for: rft

...ave a problem assigning different colors to bars in a barplot. The data I'm using is the following dataframe (truncated) : > L0 r n p t [...] 18 19 1 1 RFM 19 20 1 1 RFM 20 21 2 1 RFM 21 23 6 1 RIH 22 24 2 1 ROC 23 25 1 1 ROC 24 26 1 1 ROC 25 27 2 1 ROC 26 28 2 1 RFT 27 29 1 1 RFT 28 30 2 1 RFT 29 31 1 1 ROH [...] My barplot should display ascending bars according to L0$n. Their width depends on L0$p, which can be greater than 1. Last, I want a different color for each of the five values of L0$t. I use the following array to assign a colour for each ty...

The ioreadX() helpers have inconsistent interface. On some architectures void *__iomem address argument is a pointer to const, on some not. Implementations of ioreadX() do not modify the memory under the address so they can be converted to a "const" version for const-safety and consistency among architectures. Signed-off-by: Krzysztof Kozlowski <krzk at kernel.org> ---

The ioreadX() helpers have inconsistent interface. On some architectures void *__iomem address argument is a pointer to const, on some not. Implementations of ioreadX() do not modify the memory under the address so they can be converted to a "const" version for const-safety and consistency among architectures. Signed-off-by: Krzysztof Kozlowski <krzk at kernel.org> ---

The ioreadX() helpers have inconsistent interface. On some architectures void *__iomem address argument is a pointer to const, on some not. Implementations of ioreadX() do not modify the memory under the address so they can be converted to a "const" version for const-safety and consistency among architectures. Signed-off-by: Krzysztof Kozlowski <krzk at kernel.org> ---

On Wed, 8 Jan 2020 at 09:13, Geert Uytterhoeven <geert at linux-m68k.org> wrote: > > Hi Krzysztof, > > On Wed, Jan 8, 2020 at 9:07 AM Geert Uytterhoeven <geert at linux-m68k.org> wrote: > > On Tue, Jan 7, 2020 at 5:53 PM Krzysztof Kozlowski <krzk at kernel.org> wrote: > > > The ioread8/16/32() and others have inconsistent interface among the > >

Hi Christophe, On Wed, Jan 8, 2020 at 9:35 AM Christophe Leroy <christophe.leroy at c-s.fr> wrote: > Le 08/01/2020 ? 09:18, Krzysztof Kozlowski a ?crit : > > On Wed, 8 Jan 2020 at 09:13, Geert Uytterhoeven <geert at linux-m68k.org> wrote: > >> On Wed, Jan 8, 2020 at 9:07 AM Geert Uytterhoeven <geert at linux-m68k.org> wrote: > >>> On Tue, Jan 7,

On Wed, Jan 08, 2020 at 09:10:06AM +0100, Geert Uytterhoeven wrote: > Hi Krzysztof, > > On Tue, Jan 7, 2020 at 5:53 PM Krzysztof Kozlowski <krzk at kernel.org> wrote: > > The ioreadX() helpers have inconsistent interface. On some architectures > > void *__iomem address argument is a pointer to const, on some not. > > > > Implementations of ioreadX() do not

The ioreadX() helpers have inconsistent interface. On some architectures void *__iomem address argument is a pointer to const, on some not. Implementations of ioreadX() do not modify the memory under the address so they can be converted to a "const" version for const-safety and consistency among architectures. Signed-off-by: Krzysztof Kozlowski <krzk at kernel.org> ---

The ioreadX() helpers have inconsistent interface. On some architectures void *__iomem address argument is a pointer to const, on some not. Implementations of ioreadX() do not modify the memory under the address so they can be converted to a "const" version for const-safety and consistency among architectures. Signed-off-by: Krzysztof Kozlowski <krzk at kernel.org> ---

Hi Krzysztof, On Tue, Jan 7, 2020 at 5:53 PM Krzysztof Kozlowski <krzk at kernel.org> wrote: > The ioread8/16/32() and others have inconsistent interface among the > architectures: some taking address as const, some not. > > It seems there is nothing really stopping all of them to take > pointer to const. Shouldn't all of them take const volatile __iomem pointers? It

On Wed, Jan 8, 2020 at 9:36 AM Christophe Leroy <christophe.leroy at c-s.fr> wrote: > Le 08/01/2020 ? 09:18, Krzysztof Kozlowski a ?crit : > > On Wed, 8 Jan 2020 at 09:13, Geert Uytterhoeven <geert at linux-m68k.org> wrote: > > I'll add to this one also changes to ioreadX_rep() and add another > > patch for volatile for reads and writes. I guess your review

I've now been able to test shared-library builds: 2.0.4 2.0.5 -------------------------------------------------------------------- alpha/alpha-linux-gnu: fail: fcntl, sigint, 2c fail: sigint, 2c arm/arm-linux-gnueabi: pass pass arm/arm-linux-gnueabihf: pass pass

Hi, On Fri, Sep 22, 2023 at 2:06?PM Lyude Paul <lyude at redhat.com> wrote: > > actually very glad to see this because I think I've seen one bug in the wild > as a result of things not getting shut down :) > > Reviewed-by: Lyude Paul <lyude at redhat.com> > Tested-by: Lyude Paul <lyude at redhat.com> Any idea of where / how this patch should land. Would

Hi, On Fri, Nov 17, 2023 at 3:00?PM Doug Anderson <dianders at chromium.org> wrote: > > Hi, > > On Fri, Sep 22, 2023 at 2:06?PM Lyude Paul <lyude at redhat.com> wrote: > > > > actually very glad to see this because I think I've seen one bug in the wild > > as a result of things not getting shut down :) > > > > Reviewed-by: Lyude Paul

Hi Ben, *massive* thanks for picking up klibc work. This might motivate me to pick up some of the TODOs for it that have piled on in my TODO (but only after the freeze, I?m sorry to say, I have more to do for other packages). >And I spotted another test program that has this property (setjmptest setjmp is a good topic? I found that building mksh and running its testsuite is a good test to

Hi Krzysztof, On Tue, Jan 7, 2020 at 5:53 PM Krzysztof Kozlowski <krzk at kernel.org> wrote: > The ioreadX() helpers have inconsistent interface. On some architectures > void *__iomem address argument is a pointer to const, on some not. > > Implementations of ioreadX() do not modify the memory under the address > so they can be converted to a "const" version for

Hi Geert, Le 08/01/2020 ? 09:43, Geert Uytterhoeven a ?crit?: > Hi Christophe, > > On Wed, Jan 8, 2020 at 9:35 AM Christophe Leroy <christophe.leroy at c-s.fr> wrote: >> Le 08/01/2020 ? 09:18, Krzysztof Kozlowski a ?crit : >>> On Wed, 8 Jan 2020 at 09:13, Geert Uytterhoeven <geert at linux-m68k.org> wrote: >>>> On Wed, Jan 8, 2020 at 9:07 AM Geert

Request For Translators<g> So what I've gathered from Wikipedia is that the Greek language does not use semicolons as a separator for enumerations: http://en.wikipedia.org/wiki/Semicolon#Greek_and_Church_Slavonic | In Greek and Church Slavonic, a semicolon indicates a question, | similar to a Latin question mark.[2] To indicate a long pause or | separate sections, each with commas

On Sun, 2019-01-20 at 14:18 +0000, Thorsten Glaser wrote: > Hi Ben, > > *massive* thanks for picking up klibc work. This might motivate > me to pick up some of the TODOs for it that have piled on in my > TODO (but only after the freeze, I?m sorry to say, I have more > to do for other packages). > > >And I spotted another test program that has this property >

On Wed, Jan 08, 2020 at 09:44:36AM +0100, Arnd Bergmann wrote: > On Wed, Jan 8, 2020 at 9:36 AM Christophe Leroy <christophe.leroy at c-s.fr> wrote: > > Le 08/01/2020 ? 09:18, Krzysztof Kozlowski a ?crit : > > > On Wed, 8 Jan 2020 at 09:13, Geert Uytterhoeven <geert at linux-m68k.org> wrote: > > > I'll add to this one also changes to ioreadX_rep() and add