From: Samuel Ortiz <sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Christophe Ricard
<christophe.ricard-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-nfc-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org,
christophe-h.ricard-qxv4g6HH51o@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 00/11] Follow up patches and several new fixes
Date: Wed, 24 Sep 2014 02:04:22 +0200 [thread overview]
Message-ID: <20140924000422.GE4235@zurbaran> (raw)
In-Reply-To: <1410596933-5530-1-git-send-email-christophe-h.ricard-qxv4g6HH51o@public.gmane.org>
Hi Christophe,
On Sat, Sep 13, 2014 at 10:28:42AM +0200, Christophe Ricard wrote:
> Christophe Ricard (11):
> NFC: st21nfca: Fix few coding style issue
> NFC: st21nfca: Fix potential skb leaks in NFC-DEP code
> NFC: st21nfca: Fix recursive fault when doing p2p in target mode.
> NFC: dts: st21nfcb_i2c: Fix invalid interrupts polarity.
> NFC: st21nfcb: Fix improper management of -EREMOTEIO error code.
> NFC: st21nfcb: Fix improper ndlc T2 management
> NFC: nci: Add support for proprietary RF Protocols
> NFC: st21nfcb: Add ISO15693 Reader/Writer support
> NFC: st21nfcb: remove error output
> NFC: st21nfca: ERR_PTR vs NULL fix
> NFC: st21nfca: Fix potential double kfree_skb error
Applied, thanks a lot.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-09-24 0:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 8:28 [PATCH v2 00/11] Follow up patches and several new fixes Christophe Ricard
[not found] ` <1410596933-5530-1-git-send-email-christophe-h.ricard-qxv4g6HH51o@public.gmane.org>
2014-09-13 8:28 ` [PATCH v2 01/11] NFC: st21nfca: Fix few coding style issue Christophe Ricard
2014-09-13 8:28 ` [PATCH v2 02/11] NFC: st21nfca: Fix potential skb leaks in NFC-DEP code Christophe Ricard
2014-09-13 8:28 ` [PATCH v2 03/11] NFC: st21nfca: Fix recursive fault when doing p2p in target mode Christophe Ricard
2014-09-13 8:28 ` [PATCH v2 04/11] NFC: dts: st21nfcb_i2c: Fix invalid interrupts polarity Christophe Ricard
2014-09-13 8:28 ` [PATCH v2 05/11] NFC: st21nfcb: Fix improper management of -EREMOTEIO error code Christophe Ricard
2014-09-13 8:28 ` [PATCH v2 06/11] NFC: st21nfcb: Fix improper ndlc T2 management Christophe Ricard
2014-09-13 8:28 ` [PATCH v2 07/11] NFC: nci: Add support for proprietary RF Protocols Christophe Ricard
2014-09-13 8:28 ` [PATCH v2 08/11] NFC: st21nfcb: Add ISO15693 Reader/Writer support Christophe Ricard
2014-09-13 8:28 ` [PATCH v2 09/11] NFC: st21nfcb: remove error output Christophe Ricard
2014-09-13 8:28 ` [PATCH v2 10/11] NFC: st21nfca: ERR_PTR vs NULL fix Christophe Ricard
2014-09-13 8:28 ` [PATCH v2 11/11] NFC: st21nfca: Fix potential double kfree_skb error Christophe Ricard
2014-09-24 0:04 ` Samuel Ortiz [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=20140924000422.GE4235@zurbaran \
--to=sameo-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=christophe-h.ricard-qxv4g6HH51o@public.gmane.org \
--cc=christophe.ricard-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nfc-hn68Rpc1hR1g9hUCZPvPmw@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).