From: "John W. Linville" <linville@tuxdriver.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
netfilter-devel@vger.kernel.org, eric.dumazet@vger.kernel.org,
jpirko@redhat.com, kaber@trash.net
Subject: Re: net-next-2.6 status...
Date: Tue, 15 Mar 2011 20:13:20 -0400 [thread overview]
Message-ID: <20110316001319.GB28663@tuxdriver.com> (raw)
In-Reply-To: <20110315.160124.104058374.davem@davemloft.net>
On Tue, Mar 15, 2011 at 04:01:24PM -0700, David Miller wrote:
> John and Patrick, I assume that after today's pulls I am completely
> up to date with everything, feature wise, that will go into the merge
> window for wireless and netfilter.
Just sent a pull request for wireless-2.6 to cover a one-liner to
enable some new firmware for iwlagn -- I nearly forgot!
Thanks,
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
WARNING: multiple messages have this Message-ID (diff)
From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netfilter-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
eric.dumazet-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
jpirko-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
kaber-dcUjhNyLwpNeoWH0uzbU5w@public.gmane.org
Subject: Re: net-next-2.6 status...
Date: Tue, 15 Mar 2011 20:13:20 -0400 [thread overview]
Message-ID: <20110316001319.GB28663@tuxdriver.com> (raw)
In-Reply-To: <20110315.160124.104058374.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
On Tue, Mar 15, 2011 at 04:01:24PM -0700, David Miller wrote:
> John and Patrick, I assume that after today's pulls I am completely
> up to date with everything, feature wise, that will go into the merge
> window for wireless and netfilter.
Just sent a pull request for wireless-2.6 to cover a one-liner to
enable some new firmware for iwlagn -- I nearly forgot!
Thanks,
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:[~2011-03-16 0:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 23:01 net-next-2.6 status David Miller
2011-03-16 0:13 ` John W. Linville [this message]
2011-03-16 0:13 ` John W. Linville
2011-03-16 0:36 ` Jeff Kirsher
2011-03-16 6:50 ` Jiri Pirko
2011-03-16 7:02 ` David Miller
2011-03-16 7:38 ` Jiri Pirko
2011-03-16 8:40 ` Jiri Pirko
2011-03-16 8:40 ` Jiri Pirko
2011-03-16 8:47 ` Thomas Graf
2011-03-16 17:38 ` David Miller
2011-03-16 17:38 ` David Miller
2011-03-16 17:42 ` David Miller
2011-03-16 18:13 ` Ben Hutchings
2011-03-16 18:17 ` David Miller
2011-03-16 17:38 ` David Miller
2011-03-16 17:38 ` David Miller
2011-03-16 17:56 ` Jiri Pirko
2011-03-16 17:56 ` Jiri Pirko
2011-03-16 18:00 ` David Miller
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=20110316001319.GB28663@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@vger.kernel.org \
--cc=jpirko@redhat.com \
--cc=kaber@trash.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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.