From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
Cc: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: pull request: wireless-next-2.6 2009-02-23
Date: Thu, 26 Feb 2009 11:13:40 -0500 [thread overview]
Message-ID: <20090226161340.GA4430@tuxdriver.com> (raw)
In-Reply-To: <1235637360.29050.16.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
On Thu, Feb 26, 2009 at 12:36:00AM -0800, Johannes Berg wrote:
> On Tue, 2009-02-24 at 23:55 -0800, David Miller wrote:
> > From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
> > Date: Mon, 23 Feb 2009 22:31:53 -0800
> >
> > > On Mon, 2009-02-23 at 14:26 -0500, John W. Linville wrote:
> > >
> > > > Johannes Berg (10):
> > > > mac80211: disallow moving netns
> > > > mac80211: fix aggregation for hardware with ampdu queues
> > > > mac80211: split IBSS/managed code
> > > > genetlink: introduce pre/post methods
> > >
> > > Hold off on this please, the genetlink patch here introduced a problem
> > > with locking and I'm going to rework/fix that.
> >
> > Ok.
> >
> > In fact it's better this way, since now John can send me the pull
> > request after the net-2.6 --> net-next-2.6 merge conflicts are
> > resolved.
>
> Now I just have to get around to fixing it, it's proving to be harder
> than I thought, and I don't have much time right now.
I suppose I could just drop that one. IIRC there was another patch
from you that depended upon that one as well?
John
--
John W. Linville Someday the world will need a hero, and you
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org might be all we have. Be ready.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-02-26 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 19:26 pull request: wireless-next-2.6 2009-02-23 John W. Linville
[not found] ` <20090223192659.GB3553-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2009-02-24 6:31 ` Johannes Berg
2009-02-25 7:55 ` David Miller
[not found] ` <20090224.235510.30497146.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2009-02-26 8:36 ` Johannes Berg
[not found] ` <1235637360.29050.16.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-02-26 16:13 ` John W. Linville [this message]
[not found] ` <20090226161340.GA4430-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2009-02-26 16:47 ` Johannes Berg
2009-02-27 1:37 ` Johannes Berg
[not found] ` <1235698640.4936.6.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-02-27 3:18 ` Luis R. Rodriguez
2009-03-11 11:49 ` Johannes Berg
[not found] ` <1236772199.20266.3.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-03-11 16:27 ` Luis R. Rodriguez
2009-02-27 20:40 ` John W. Linville
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=20090226161340.GA4430@tuxdriver.com \
--to=linville-2xusbdqka4r54taoqtywwq@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).