netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
To: linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
Cc: linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: pull request: wireless-next 2012-01-05
Date: Thu, 05 Jan 2012 12:30:39 -0500 (EST)	[thread overview]
Message-ID: <20120105.123039.977245333906219511.davem@davemloft.net> (raw)
In-Reply-To: <20120105160938.GC10666-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>

From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
Date: Thu, 5 Jan 2012 11:09:38 -0500

> Here is the last wireless "feature" pull request intended for 3.3.
> Mostly minutia, but highlights include an NFC spec update and some
> relicensing of regulatory code under the ISC license.
> 
> After consulation with Kalle, I have reverted the ath6kl USB bits that
> were causing build problems.
> 
> Please let me know if there are problems!
> 
> John
> 
> P.S. Sorry about the "ssh://" URL -- git.kernel.org seems a bit slow
> about syncing today...

That ssh URL would only work for you, since I don't have permission to get
at your trees even just to pull.

I pulled from the equivalent git:// URL, the top commit was the ath6kl
USB revert.
--
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:[~2012-01-05 17:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05 16:09 pull request: wireless-next 2012-01-05 John W. Linville
     [not found] ` <20120105160938.GC10666-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2012-01-05 17:30   ` David Miller [this message]
2012-01-05 17:49     ` 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=20120105.123039.977245333906219511.davem@davemloft.net \
    --to=davem-ft/pcqaiutieiz0/mpfg9q@public.gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linville-2XuSBdqkA4R54TAoqtyWWQ@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).