From: "John W. Linville" <linville@tuxdriver.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Linux Wireless <linux-wireless@vger.kernel.org>,
Linux NFC <linux-nfc@ml01.01.org>
Subject: Re: [GIT] [NFC] 3.11 fixes
Date: Wed, 31 Jul 2013 15:15:52 -0400 [thread overview]
Message-ID: <20130731191551.GF2311@tuxdriver.com> (raw)
In-Reply-To: <20130730235915.GA4641@zurbaran>
On Wed, Jul 31, 2013 at 01:59:15AM +0200, Samuel Ortiz wrote:
> Hi John,
>
> This is the second NFC fixes pull request for 3.11.
>
> We have:
>
> 1) A build failure fix for the NCI SPI transport layer due to a
> missing CRC_CCITT Kconfig dependency.
>
> 2) A netlink command rename: CMD_FW_UPLOAD was merged during the 3.11
> merge window but the typical terminology for loading a firmware to a
> target is firmware download rather than upload. In order to avoid any
> confusion in a file exported to userspace, we rename this command to
> CMD_FW_DOWNLOAD.
>
> I realize 2) might not meet the net.git criteria for what fixes are. If
> you don't want to take it then I'll have to push it through the
> 3.12 merge window. If that's the case, and you only want to take 1) then
> please use tags/nfc-3.11-1 instead of tags/nfc-3.11-2 in your pull URL.
>
> The following changes since commit 64b6f46f1141ad938e354f37af62e28da972e8eb:
>
> ath9k_hw: Fix multicast search for AR9002 family (2013-07-18 16:22:00 -0400)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/sameo/nfc-fixes.git tags/nfc-fixes-3.11-2
>
> for you to fetch changes up to 9ea7187c53f63e31f2d1b2b1e474e31808565009:
>
> NFC: netlink: Rename CMD_FW_UPLOAD to CMD_FW_DOWNLOAD (2013-07-31 01:19:43 +0200)
Pulling now...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2013-07-31 19:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 23:59 [GIT] [NFC] 3.11 fixes Samuel Ortiz
2013-07-31 19:15 ` 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=20130731191551.GF2311@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-nfc@ml01.01.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sameo@linux.intel.com \
/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).