From: Harvey Harrison <harvey.harrison@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Jiri Kosina <jkosina@suse.cz>, Jiri Benc <jbenc@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH-mm 1/3] mac80211: tkip.c use get/put_unaligned helpers
Date: Thu, 17 Apr 2008 10:22:26 -0700 [thread overview]
Message-ID: <1208452946.17196.1.camel@brick> (raw)
In-Reply-To: <1208450454.4066.20.camel@johannes.berg>
On Thu, 2008-04-17 at 18:40 +0200, Johannes Berg wrote:
> > > I guess you are going to push this stuff through -mm altogether, right?
> > > I can hardly take this into my tree right now, as the helpers are not in
> > > Linus' tree yet.
> >
> > yeah, sorry, that's been confusing a few people.
> >
> > Strictly I'd merge the core infrastructure and then send the dependent
> > patches into the relevant maintainers. But that can mean than we
> > needlessly miss the merge window, so it's most parctical to send along an
> > acked-by and I'll merge the dependent patch directly with the appropriate
> > ordering.
>
> I guess what Jiri (Benc) is saying that *I* should ack them, not him.
> Jiri (Benc), maybe you care to move yourself down in the maintainers
> file?
I'll resubmit a cleaned up series anyways once the unaligned access
helpers get into mainline, so don't worry too much about this set I
suppose.
Cheers,
Harvey
prev parent reply other threads:[~2008-04-17 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1208370570.11920.107.camel@brick>
2008-04-17 8:58 ` [PATCH-mm 1/3] mac80211: tkip.c use get/put_unaligned helpers Jiri Benc
2008-04-17 9:04 ` Jiri Kosina
2008-04-17 16:40 ` Johannes Berg
2008-04-17 17:22 ` Harvey Harrison [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=1208452946.17196.1.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jbenc@suse.cz \
--cc=jkosina@suse.cz \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).