From: "John W. Linville" <linville@tuxdriver.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ][Patch] alter prototypes in airo.c platform.h
Date: Sat, 25 Feb 2006 04:18:47 +0000 [thread overview]
Message-ID: <20060225041842.GA21902@tuxdriver.com> (raw)
In-Reply-To: <1140516994.7780.37.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
On Sat, Feb 25, 2006 at 11:39:13AM +1100, Darren Jenkins" wrote:
> On Fri, 2006-02-24 at 16:46 -0500, John W. Linville wrote:
> > On Tue, Feb 21, 2006 at 09:16:34PM +1100, Darren Jenkins" wrote:
> > >
> > > Signed-off-by: Darren Jenkins <darrenrjenkins@gmail.com>
> > Acked-by: John W. Linville <linville@tuxdriver.com>
> >
> > Do I need to merge the airo hunk?
> >
> > John
>
> Do you mean the platform.h hunk ?
> I would not expect you merge the platform.h part as I don't think it has
> anything to do with you. I did not cc the maintainer for that bit
> because I could not figure out who it was.
Well, I guess I meant that it's OK for whoever merges the other part
to merge the airo part as well. But, if they were expecting me to
merge the airo part (or the whole thing), they need to let me know.
> I included the two changes together to cut down on the number of emails
> with small changes. Perhaps that was a "bad idea" on my part.
You probably did the right thing, I just wanted to clarify who was
merging what so that your patch didn't get dropped.
John
--
John W. Linville
linville@tuxdriver.com
[-- Attachment #2: Type: text/plain, Size: 168 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
prev parent reply other threads:[~2006-02-25 4:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 10:16 [KJ][Patch] alter prototypes in airo.c platform.h Darren Jenkins\
2006-02-24 21:46 ` John W. Linville
2006-02-25 0:39 ` Darren Jenkins\
2006-02-25 4:18 ` John W. Linville [this message]
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=20060225041842.GA21902@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=kernel-janitors@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.