netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: pull request: wireless-next-2.6 2008-05-22
Date: Tue, 3 Jun 2008 14:53:01 -0400	[thread overview]
Message-ID: <20080603185301.GA28966@tuxdriver.com> (raw)
In-Reply-To: <20080522124017.GA3996-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>

On Thu, May 22, 2008 at 08:40:17AM -0400, John W. Linville wrote:
> Dave,
> 
> Another week, another 70+ patches -- actually this pace feels a
> bit slow!  This batch includes updates to rt2x00, libertas, iwlwifi,
> mac80211, and a smattering of other drivers.
> 
> Let me know if there are problems!
> 
> John
> 
> ---
> 
> Individual patches are available here:
> 
> 	http://www.kernel.org/pub/linux/kernel/people/linville/wireless-next-2.6/
> 
> ---
> 
> The following changes since commit 5b06c85c3b96fa8db632f1ee94f99a2bd0215f3a:
>   Allan Stephens (1):
>         tipc: Cosmetic cleanup of topology service code
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next-2.6.git master

It seems you haven't pulled this yet.  I'll presume that is just due
to your itinerary or whatever else might keep you busy.  If there is
some reason then let me know!

In the meantime, I'll soon post another pull request.  If for some
reason you want to pull this one but not the new one, this HEAD is
tagged as "master-2008-05-21" in the wireless-next-2.6 tree as well.

Thanks,

John
-- 
John W. Linville
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
--
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

  parent reply	other threads:[~2008-06-03 18:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-22 12:40 pull request: wireless-next-2.6 2008-05-22 John W. Linville
     [not found] ` <20080522124017.GA3996-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-06-03 18:53   ` John W. Linville [this message]
     [not found]     ` <20080603185301.GA28966-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-06-03 19:49       ` pull request: wireless-next-2.6 2008-06-03 John W. Linville
     [not found]         ` <20080603194927.GA9590-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-06-09 20:42           ` John W. Linville
     [not found]             ` <20080609204241.GA11343-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-06-09 21:07               ` pull request: wireless-next-2.6 2008-06-09 John W. Linville
2008-06-10  9:19                 ` David Miller
2008-06-10 12:17                   ` 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=20080603185301.GA28966@tuxdriver.com \
    --to=linville-2xusbdqka4r54taoqtywwq@public.gmane.org \
    --cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@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).