From: Borislav Petkov <petkov@math.uni-muenster.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: David Rientjes <rientjes@cs.washington.edu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched.c : correct comment for this_rq_lock() routine
Date: Tue, 31 Oct 2006 16:30:21 +0100 [thread overview]
Message-ID: <20061031153021.GA14505@gollum.tnic> (raw)
In-Reply-To: <Pine.LNX.4.64.0610301623360.13169@localhost.localdomain>
On Mon, Oct 30, 2006 at 04:34:08PM -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.
In case you're still doubtful about volunteering:
http://lkml.org/lkml/2004/12/20/255
--
Regards/Gruß,
Boris.
next prev parent reply other threads:[~2006-10-31 15:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 21:02 Robert P. J. Day
2006-10-30 21:08 ` David Rientjes
2006-10-30 21:34 ` Robert P. J. Day
2006-10-30 22:05 ` Björn Steinbrink
2006-10-31 15:30 ` Borislav Petkov [this message]
2006-10-31 18:11 ` Robert P. J. Day
2006-10-31 22:46 ` Nick Piggin
2006-11-01 8:01 ` Robert P. J. Day
2006-11-01 8:13 ` Nick Piggin
2006-11-01 12:27 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061031153021.GA14505@gollum.tnic \
--to=petkov@math.uni-muenster.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@cs.washington.edu \
--cc=rpjday@mindspring.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®