All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: David Miller <davem@davemloft.net>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: pull request: wireless-next 2012-01-05
Date: Thu, 5 Jan 2012 12:49:07 -0500	[thread overview]
Message-ID: <20120105174906.GD10666@tuxdriver.com> (raw)
In-Reply-To: <20120105.123039.977245333906219511.davem@davemloft.net>

On Thu, Jan 05, 2012 at 12:30:39PM -0500, David Miller wrote:
> From: "John W. Linville" <linville@tuxdriver.com>
> 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.

Hmmm...really?  I'm pretty sure I pulled other trees that way.

> I pulled from the equivalent git:// URL, the top commit was the ath6kl
> USB revert.

Sure, that's fine.

Thanks!

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

      reply	other threads:[~2012-01-05 18:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05 16:09 pull request: wireless-next 2012-01-05 John W. Linville
2012-01-05 16:09 ` John W. Linville
2012-01-05 17:30 ` David Miller
2012-01-05 17:30   ` David Miller
2012-01-05 17:49   ` John W. Linville [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=20120105174906.GD10666@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=davem@davemloft.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@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.