linux-kernel - Re: [PATCH] sched.c : correct comment for this_rq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 30 Oct 2006 23:05:51 +0100
From:	Björn Steinbrink <B.Steinbrink@....de>
To:	"Robert P. J. Day" <rpjday@...dspring.com>
Cc:	David Rientjes <rientjes@...washington.edu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	trivial@...nel.org
Subject: Re: [PATCH] sched.c : correct comment for this_rq_lock() routine

On 2006.10.30 16:34:08 -0500, Robert P. J. Day wrote:
> On Mon, 30 Oct 2006, David Rientjes wrote:
> 
> > On Mon, 30 Oct 2006, Robert P. J. Day wrote:
> >
> > >
> > > Correct the comment for the this_rq_lock() routine.
> > >
> >
> > You submitted this same patch two days ago.
> >
> > 		http://lkml.org/lkml/2006/10/28/54
> 
> that's right, i did.  and given that it was a trivial, aesthetic patch
> but a couple "git pull" cycles went by without it being applied, i
> figured i might as well submit it again.
> 
> quite honestly, at this point, given that it's this much trouble to
> fix a freaking comment in a single file, i'm seriously losing interest
> in wasting any more of my time at this.  life is just too short to
> volunteer unpaid labour that just gets dropped on the floor because
> you don't know the secret handshake.

You CC'd trivial@...nel.org, so you've probably read
http://www.kernel.org/pub/linux/kernel/people/bunk/trivial/
which clearly says that it most likely will go into 2.6.20(-rc1). So
your "git pull" tests tell nothing...

I have never submitted a patch to trivial@, so I have no idea if you get
any kind of confirmation that it will be included, but if you get none,
you should probably just assume that it will be included.

Also, you should just take David's reply as a confirmation that your
patch didn't get lost in the noise but was seen by someone. Of course
you should also remember to not re-submit patches that quick, especially
if there is only a weekend in between the two submissions...

Björn
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/