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 for Android: free password hash cracker in your pocket

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

Message-ID: <Pine.LNX.4.64.0610301623360.13169@localhost.localdomain>
Date:	Mon, 30 Oct 2006 16:34:08 -0500 (EST)
From:	"Robert P. J. Day" <rpjday@...dspring.com>
To:	David Rientjes <rientjes@...washington.edu>
cc:	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 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.

rday
-
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/