On 14/01/2019 18:05, Jens Axboe wrote:
On 1/14/19 11:05 AM, Christoph Hellwig wrote:
On Mon, Jan 14, 2019 at 11:02:07AM -0700, Keith Busch wrote:
User fin4478 informs me Ming's patch above fixes
the warnings, but responding to the mailing lists from that email account
are blocked for "security
On 1/14/19 11:05 AM, Christoph Hellwig wrote:
> On Mon, Jan 14, 2019 at 11:02:07AM -0700, Keith Busch wrote:
>> User fin4478 informs me Ming's patch above fixes
>> the warnings, but responding to the mailing lists from that email account
>> are blocked for "security or policy reasons" and requeste
On Mon, Jan 14, 2019 at 11:02:07AM -0700, Keith Busch wrote:
> User fin4478 informs me Ming's patch above fixes
> the warnings, but responding to the mailing lists from that email account
> are blocked for "security or policy reasons" and requested I forward
> the successful test result.
>
> Chri
[+linux-n...@lists.infradead.org]
On Mon, Jan 14, 2019 at 10:03:39AM -0700, Keith Busch wrote:
> [+Ming]
> On Mon, Jan 14, 2019 at 08:31:45AM -0600, Bjorn Helgaas wrote:
> > [+cc Dou, Jens, Thomas, Christoph, linux-pci, LKML]
> >
> > On Sun, Jan 13, 2019 at 11:24 PM fin4478 fin4478
> > wrote:
>
[+Ming]
On Mon, Jan 14, 2019 at 08:31:45AM -0600, Bjorn Helgaas wrote:
> [+cc Dou, Jens, Thomas, Christoph, linux-pci, LKML]
>
> On Sun, Jan 13, 2019 at 11:24 PM fin4478 fin4478 wrote:
> >
> > Hi,
> >
> > A regression from the 4.20 kernel: I have the Asgard 256GB nvme drive
> > and my custom non
[+cc Dou, Jens, Thomas, Christoph, linux-pci, LKML]
On Sun, Jan 13, 2019 at 11:24 PM fin4478 fin4478 wrote:
>
> Hi,
>
> A regression from the 4.20 kernel: I have the Asgard 256GB nvme drive
> and my custom non debug 1000Hz timer kernel 5.0 started to throw a
> couple of warning messages at boot.
On Sun, Sep 13, 2015 at 9:24 PM, Ken Moffat wrote:
> On Sun, Sep 13, 2015 at 08:06:02PM -0300, Diego Viola wrote:
>> Hello,
>>
>> Can someone please remove this commit from the repo:
>>
>> https://git.kernel.org/cgit/linux/kernel/git/to
On Sun, Sep 13, 2015 at 08:06:02PM -0300, Diego Viola wrote:
> Hello,
>
> Can someone please remove this commit from the repo:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/README?id=6609b638353c99c5736e05abd17197f1cb776e0e
>
> I made a huge
Hello,
Can someone please remove this commit from the repo:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/README?id=6609b638353c99c5736e05abd17197f1cb776e0e
I made a huge grammar mistake in my commit message that I can't
forget, it makes me feel terrible and I
Hi Artem,
On Thu, 9 Jan 2014 16:33:21 + "Bityutskiy, Artem"
wrote:
>
> could you please remove the UBI git tree from linux-next?
>
> git://git.infradead.org/linux-ubi
>
> I will use the UBIFS git tree for both UBI and UBIFS patches from now
> on. The traffic
Hi Stephen,
could you please remove the UBI git tree from linux-next?
git://git.infradead.org/linux-ubi
I will use the UBIFS git tree for both UBI and UBIFS patches from now
on. The traffic became so low that it does not make sense to keep 2
separate trees for these very related subsystems
On Sun, 12 Aug 2007, Andi Kleen wrote:
>
> Can you double check? I have a hard time believing it.
Andi, read the code. The old code was fine. Your patch was the culprit.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On 12 Aug 2007 15:55:50 +0200
Andi Kleen <[EMAIL PROTECTED]> wrote:
> > > Ok Linus already applied your patch. Even though it's a really bad
> > > fragile hack, not better than the old bug.
> > > Petr are you double sure you really tested with
> > > ab144f5ec64c42218a555ec1dbde6b60cf2982d6
> > > a
Petr Vandrovec <[EMAIL PROTECTED]> writes:
> Andi Kleen wrote:
> > On Sunday 12 August 2007 10:12, Petr Vandrovec wrote:
> >> Hello,
> >> after I upgraded kernel on my box to current git, only thing it did
> >> was rebooting in a loop. After some digging I found that it is silly
> >> to apply a
Andi Kleen wrote:
On Sunday 12 August 2007 10:12, Petr Vandrovec wrote:
Hello,
after I upgraded kernel on my box to current git, only thing it did
was rebooting in a loop. After some digging I found that it is silly
to apply alternative to memcpy by using that every same memcpy...
Sorry if it
On Sunday 12 August 2007 10:12, Petr Vandrovec wrote:
> Hello,
> after I upgraded kernel on my box to current git, only thing it did
> was rebooting in a loop. After some digging I found that it is silly
> to apply alternative to memcpy by using that every same memcpy...
> Sorry if it is known b
Rob Prowel wrote:
[1.] One line summary of the problem:
2.4 and 2.6 kernel headers use c++ reserved word "new"
as identifier in function prototypes.
Yes, the kernel is written in C, not C++.
using the identifier "new" in kernel headers that are
visible to applications programs is a bad i
On 06/07/05, Rob Prowel <[EMAIL PROTECTED]> wrote:
> 2.4 and 2.6 kernel headers use c++ reserved word "new"
> as identifier in function prototypes.
> [...]
> While not an error, per se, it is kind of sloppy and
> it is amazing that it hasn't shown up before now.
> using the identifier "new" in kern
On Wed, 6 Jul 2005, Alexey Dobriyan wrote:
On Wednesday 06 July 2005 13:26, Rob Prowel wrote:
When kernel headers are included in compilation of c++
programs the compile fails because some header files
use "new" in a way that is illegal for c++. This
shows up when compiling mySQL under linux 2
On Wed, Jul 06, 2005 at 02:26:57AM -0700, Rob Prowel wrote:
> [1.] One line summary of the problem:
>
> 2.4 and 2.6 kernel headers use c++ reserved word "new"
> as identifier in function prototypes.
Correction:
[1.] One line summary of problem:
Userspace application is making use of private
On Wed, 2005-07-06 at 02:26 -0700, Rob Prowel wrote:
> While not an error, per se, it is kind of sloppy and
> it is amazing that it hasn't shown up before now.
> using the identifier "new" in kernel headers that are
> visible to applications programs is a bad idea.
It _is_ an error, on mysql's pa
On Wednesday 06 July 2005 13:26, Rob Prowel wrote:
> When kernel headers are included in compilation of c++
> programs the compile fails because some header files
> use "new" in a way that is illegal for c++. This
> shows up when compiling mySQL under linux 2.6. It
> uses $KERNELSOURCE/include/as
On 7/6/05, Rob Prowel <[EMAIL PROTECTED]> wrote:
> [1.] One line summary of the problem:
>
> 2.4 and 2.6 kernel headers use c++ reserved word "new"
> as identifier in function prototypes.
>
"new" is not a reserved word in C. the kernel is written in C.
> [2.] Full description of the problem/rep
On Wed, Jul 06, 2005 at 02:26:57AM -0700, Rob Prowel wrote:
> [1.] One line summary of the problem:
>
> 2.4 and 2.6 kernel headers use c++ reserved word "new"
> as identifier in function prototypes.
>
This is a FAQ.
1) kernel headers are for kernel use.
2) the kernel is written in C, not C++
[1.] One line summary of the problem:
2.4 and 2.6 kernel headers use c++ reserved word "new"
as identifier in function prototypes.
[2.] Full description of the problem/report:
When kernel headers are included in compilation of c++
programs the compile fails because some header files
use "new
Please remove [EMAIL PROTECTED] from this list as he is no longer an
employee at this company.
Thank you
Mike Cutler
Postmaster
Pacific Data Images
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordo
26 matches
Mail list logo
