From: Samuel Ortiz <sameo@linux.intel.com>
To: Joe Perches <joe@perches.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Linux NFC <linux-nfc@lists.01.org>,
Linux Wireless <linux-wireless@vger.kernel.org>
Subject: Re: [GIT] [3.12] NFC updates
Date: Fri, 16 Aug 2013 17:20:02 +0200 [thread overview]
Message-ID: <20130816152002.GG21350@zurbaran> (raw)
In-Reply-To: <1376536069.1949.124.camel@joe-AO722>
Hi Joe,
On Wed, Aug 14, 2013 at 08:07:49PM -0700, Joe Perches wrote:
> On Thu, 2013-08-15 at 01:04 +0200, Samuel Ortiz wrote:
> > Hi John,
> >
> > This is the first NFC pull request for the 3.12 release.
>
> Any reason why these reformatting patches were
> not applied?
For some reasons they got lost in my inbox, sorry about that.
I'll review and queue them as soon as I get back to my linux-nfc backlog
(I just got back from vacation today).
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2013-08-16 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 23:04 [GIT] [3.12] NFC updates Samuel Ortiz
2013-08-15 3:07 ` Joe Perches
2013-08-16 15:20 ` Samuel Ortiz [this message]
2013-08-15 19:56 ` 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=20130816152002.GG21350@zurbaran \
--to=sameo@linux.intel.com \
--cc=joe@perches.com \
--cc=linux-nfc@lists.01.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).