On Sat, Feb 27, 2021 at 02:02:21AM +0300, Alexey Dobriyan wrote:
> There are rules and schemes about how to create guard macro.
>
> Should it be prefixed by underscore?
> Should it be prefixed by two underscores?
> Should it be full path uppercased or just last path component?
> Should the guard
From: Alexey Dobriyan
> Sent: 26 February 2021 23:02
>
> On Fri, Feb 26, 2021 at 01:53:48PM -0800, Linus Torvalds wrote:
> > On Fri, Feb 26, 2021 at 12:17 PM Alexey Dobriyan
> > wrote:
> > >
> > > I want to sent treewide "#pragma once" conversion:
> >
> > Are there *any* advantages to it?
> >
>
On Fri, Feb 26, 2021 at 01:53:48PM -0800, Linus Torvalds wrote:
> On Fri, Feb 26, 2021 at 12:17 PM Alexey Dobriyan wrote:
> >
> > I want to sent treewide "#pragma once" conversion:
>
> Are there *any* advantages to it?
>
> It's non-standard,
It is effectively standard:
https://en.wikipedia.org/
On Fri, Feb 26, 2021 at 12:17 PM Alexey Dobriyan wrote:
>
> I want to sent treewide "#pragma once" conversion:
Are there *any* advantages to it?
It's non-standard, and the historical argument for it ("it can reduce
compile times because the preprocessor doesn't open the file twice" is
pure and u
Linus wrote:
> I'm hoping to just do -rc1 this weekend after all - despite my late
> start due to loss of power for several days.
>
> I'll allow late stragglers with good reason through, but the fewer of
> those there are, the better, of course.
I want to sent treewide "#pragma once" conversion:
On 7/19/19 12:56 AM, Andrew Morton wrote:
>
> The rest of MM and a kernel-wide procfs cleanup.
>
>
>
> Summary of the more significant patches:
Thanks for that!
Perhaps now it would be nice if this went also to linux-mm and lkml, as
mm-commits is sort of hidden.
Vlastimil
On 7/17/19 6:13 PM, Linus Torvalds wrote:
> On Wed, Jul 17, 2019 at 1:47 AM Vlastimil Babka wrote:
>>
>> So I've tried now to provide an example what I had in mind, below.
>
> I'll take it as a trial. I added one-line notes about coda and the
> PTRACE_GET_SYSCALL_INFO interface too.
Thanks.
> I
On Wed, Jul 17, 2019 at 09:13:26AM -0700, Linus Torvalds wrote:
> On Wed, Jul 17, 2019 at 1:47 AM Vlastimil Babka wrote:
> >
> > So I've tried now to provide an example what I had in mind, below.
>
> I'll take it as a trial. I added one-line notes about coda and the
> PTRACE_GET_SYSCALL_INFO inte
On Wed, Jul 17, 2019 at 1:47 AM Vlastimil Babka wrote:
>
> So I've tried now to provide an example what I had in mind, below.
I'll take it as a trial. I added one-line notes about coda and the
PTRACE_GET_SYSCALL_INFO interface too.
I do hope that eventually I'll just get pull requests, and they'
Cool !!
On 10:47 Wed 17 Jul , Vlastimil Babka wrote:
On 7/17/19 1:25 AM, Andrew Morton wrote:
Most of the rest of MM and just about all of the rest of everything
else.
Hi,
as I've mentioned at LSF/MM [1], I think it would be nice if mm pull
requests had summaries similar to other subsys
On 7/17/19 1:25 AM, Andrew Morton wrote:
>
> Most of the rest of MM and just about all of the rest of everything
> else.
Hi,
as I've mentioned at LSF/MM [1], I think it would be nice if mm pull
requests had summaries similar to other subsystems. I see they are now
more structured (thanks!), but
* Pavel Machek [180508 21:53]:
> Hi!
>
> I have problems with incoming SMS. ofono tries to use +CNMI=1,2,2,1,0
>
> > AT+CNMI=?
> < +CNMI: (0,1,2),(0,1,2,3),(0,2),(0,1,2),(0,1)
> < OK
> ofonod[3070]: drivers/atmodem/sms.c:build_cnmi_string()
> ofonod[3070]: drivers/atmodem/sms.c:construct_ack_pdu
Hi Chris,
On Wed, 18 May 2016 17:10:43 -0400 Chris Mason wrote:
>
> Dave Sterba's tree in linux-next has a few btrfs patches that we're not
> sending yet into Linus. We've got an update for Josef's enospc work
> that'll get sent in next week.
>
> So he prepped a pull for me that merged up a num
On Wed, May 18, 2016 at 05:10:43PM -0400, Chris Mason wrote:
> Dave Sterba's tree in linux-next has a few btrfs patches that we're not
> sending yet into Linus. We've got an update for Josef's enospc work
> that'll get sent in next week.
>
> So he prepped a pull for me that merged up a number of
On Thu, Sep 10 2015, Linus Torvalds wrote:
> The VERY FIRST conversion patch I looked at was buggy. That makes me
> angry. The whole *AND*ONLY* point of this whole thing was to get rid
> of bugs, and be a obviously safe interface, and then the first
> conversion patch proves it wrong.
>
> Let me
On Wed, Sep 9, 2015 at 3:34 PM, Andrew Morton wrote:
> Subject: lib/: add parse_integer() (replacement for simple_strto*())
> Subject: parse_integer: add runtime testsuite
> Subject: parse-integer: rewrite kstrto*()
> Subject: parse_integer: add checkpatch.pl notice
> Subject: parse_integer: conve
> ABI changes are not a problem for -stable, so don't let that stop anyone
> :)
In fact this is the harmless sort (changes only the error code of a
failure case) that might actually go in if there were any important
reason. But the smiley stands.
Thanks,
Roland
-
To unsubscribe from this list:
On Fri, May 04, 2007 at 11:57:21AM -0700, Roland McGrath wrote:
> > Ah. The patch affects security code, but it doesn't actually address any
> > insecurity. I didn't think it was needed for -stable?
>
> I would not recommend it for -stable.
> It is an ABI change for the case of a security refu
> Ah. The patch affects security code, but it doesn't actually address any
> insecurity. I didn't think it was needed for -stable?
I would not recommend it for -stable.
It is an ABI change for the case of a security refusal.
Thanks,
Roland
-
To unsubscribe from this list: send the line "unsu
On Fri, May 04, 2007 at 09:14:34AM -0700, Andrew Morton wrote:
> On Fri, 4 May 2007 06:37:28 -0700 Greg KH <[EMAIL PROTECTED]> wrote:
>
> > On Wed, May 02, 2007 at 03:02:52PM -0700, Andrew Morton wrote:
> > > - One little security patch
> >
> > Care to cc: linux-stable with it so we can do a new
On Fri, 4 May 2007 06:37:28 -0700 Greg KH <[EMAIL PROTECTED]> wrote:
> On Wed, May 02, 2007 at 03:02:52PM -0700, Andrew Morton wrote:
> > - One little security patch
>
> Care to cc: linux-stable with it so we can do a new 2.6.21 release with
> it if needed?
>
Ah. The patch affects security cod
On Wed, May 02, 2007 at 03:02:52PM -0700, Andrew Morton wrote:
> - One little security patch
Care to cc: linux-stable with it so we can do a new 2.6.21 release with
it if needed?
thanks,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message t
On Thu, 3 May 2007 08:55:43 +0100 Russell King <[EMAIL PROTECTED]> wrote:
> On Wed, May 02, 2007 at 03:02:52PM -0700, Andrew Morton wrote:
> > So this is what I have lined up for the first mm->2.6.22 batch. I won't be
> > sending it off for another 12-24 hours yet. To give people time for final
On Wed, May 02, 2007 at 03:02:52PM -0700, Andrew Morton wrote:
> So this is what I have lined up for the first mm->2.6.22 batch. I won't be
> sending it off for another 12-24 hours yet. To give people time for final
> comment and to give me time to see if it actually works.
I assume you're going
On Wed, 2007-05-02 at 15:02 -0700, Andrew Morton wrote:
> So this is what I have lined up for the first mm->2.6.22 batch. I won't be
> sending it off for another 12-24 hours yet. To give people time for final
> comment and to give me time to see if it actually works.
Thanks.
I have some powerpc
> Looks like Andrew's patch bomb script needs some rate limiting ;-)
sendpatchset has that, already builtin ;)
http://www.speakeasy.org/~pj99/sgi/sendpatchset
Though the 5 second delay might not be enough for someone
publishing at the rate Andrew does.
--
I won't rest
Andrew wrote:
> I never got around to setting that up, plus the Subject:s pretty quickly
> become invisible when they're indented 198 columns in GUI MUAs.
My sendpatchset tool should be good for this. It sends all but the
first message are sent in "Reference" to, and "In-Reply-To" the first
messa
On Thu, 2005-04-14 at 13:48 +0200, Geert Uytterhoeven wrote:
> On Tue, 12 Apr 2005, Andrew Morton wrote:
> > As the commits list probably isn't working at present I'll cc linux-kernel
> > on this lot. Fairly cruel, sorry, but I don't like the idea of people not
> > knowing what's hitting the main
Geert Uytterhoeven wrote:
On Tue, 12 Apr 2005, Andrew Morton wrote:
As the commits list probably isn't working at present I'll cc linux-kernel
on this lot. Fairly cruel, sorry, but I don't like the idea of people not
knowing what's hitting the main tree.
Is it me, or were really only 117 mails of
On Tue, 12 Apr 2005, Andrew Morton wrote:
> As the commits list probably isn't working at present I'll cc linux-kernel
> on this lot. Fairly cruel, sorry, but I don't like the idea of people not
> knowing what's hitting the main tree.
Is it me, or were really only 117 mails of the 198 sent to lkm
Russell King <[EMAIL PROTECTED]> wrote:
>
> I don't see a patch which adds linux/pm.h to linux/sysdev.h, which is
> required to fix ARM builds in -rc2 and onwards kernels.
That fix is buried in [patch 105/198]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body o
On Tue, Apr 12, 2005 at 02:08:00PM -0700, Andrew Morton wrote:
> Russell King <[EMAIL PROTECTED]> wrote:
> >
> > I don't see a patch which adds linux/pm.h to linux/sysdev.h, which is
> > required to fix ARM builds in -rc2 and onwards kernels.
>
> That fix is buried in [patch 105/198]
Great, than
On Tue, Apr 12, 2005 at 03:23:22AM -0700, Andrew Morton wrote:
> As the commits list probably isn't working at present I'll cc linux-kernel
> on this lot. Fairly cruel, sorry, but I don't like the idea of people not
> knowing what's hitting the main tree.
I don't see a patch which adds linux/pm.h
Hi, Andrew Morton schrub am Tue, 12 Apr 2005 04:10:45 -0700:
> David Vrabel <[EMAIL PROTECTED]> wrote:
>>
>> Is there any chance that in the future that these patch sets get posted
>> all to one thread?
>
> I never got around to setting that up, plus the Subject:s pretty quickly
> become invis
Andrew Morton wrote:
As the commits list probably isn't working at present I'll cc linux-kernel
on this lot. Fairly cruel, sorry, but I don't like the idea of people not
knowing what's hitting the main tree.
I'd like to second the idea of having all the patches be replies to this
original posting
Andrew Morton wrote:
> As the commits list probably isn't working at present I'll cc linux-kernel
> on this lot. Fairly cruel, sorry, but I don't like the idea of people not
> knowing what's hitting the main tree.
Is there any chance that in the future that these patch sets get posted
all to one
Andrew Morton wrote:
> David Vrabel <[EMAIL PROTECTED]> wrote:
>
>>Is there any chance that in the future that these patch sets get posted
>> all to one thread?
>
> I never got around to setting that up, plus the Subject:s pretty quickly
> become invisible when they're indented 198 columns in GUI
David Vrabel <[EMAIL PROTECTED]> wrote:
>
> Is there any chance that in the future that these patch sets get posted
> all to one thread?
I never got around to setting that up, plus the Subject:s pretty quickly
become invisible when they're indented 198 columns in GUI MUAs.
Hopefully we'll have t
Hello!
> I've scrolled through various code in net/ipv4, and I can't see how to query
> the TOS of an incoming TCP stream (or at the least, the TOS of the SYN which
> initiated the connection).
No way. Formally it is IP_RECVTOS, followed by IP_PKTOPTIONS.
But getting TOS via IP_PKTOPTIONS is no
> getsockopt(fd, SOL_IP, IP_TOS, ..
Doesn't work. Returns the TOS of outgoing packets, which defaults to 0 even if
there is a TOS set on incoming traffic... that was what I tried in my first
test program.
David.
> cheers,
>
> lincoln.
>
> At 03:00 PM 7/03/2001 +1100, David Luyer wrote:
>
>
getsockopt(fd, SOL_IP, IP_TOS, ..
cheers,
lincoln.
At 03:00 PM 7/03/2001 +1100, David Luyer wrote:
>I've scrolled through various code in net/ipv4, and I can't see how to query
>the TOS of an incoming TCP stream (or at the least, the TOS of the SYN which
>initiated the connection).
>
>Someone
41 matches
Mail list logo
