From: Christophe Ricard <christophe.ricard-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org
Cc: linux-nfc-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org,
christophe.ricard-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
christophe-h.ricard-qxv4g6HH51o@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH 00/11] Follow up patches and several new fixes
Date: Fri, 12 Sep 2014 21:49:30 +0200 [thread overview]
Message-ID: <1410551381-7565-1-git-send-email-christophe-h.ricard@st.com> (raw)
Hi,
Please find in those patches a set of followup items according to
previous submissions feedback:
- NFC: st21nfca: Fix few coding style issue
- NFC: st21nfca: Fix potential skb leaks in NFC-DEP code
- NFC: st21nfca: Fix potential double kfree_skb error
are patches related to previous patch:
[PATCH 2/8] NFC: st21nfca: Fix potential skb leaks in NFC-DEP code
NFC: st21nfca: Replace all remaining IS_ERR(skb) with !skb is related
with [PATCH 4/5] NFC: st21nfca: Remove all remaining IS_ERR(skb) for
simple !skb condition.
I have tried to review again and add some more explanation. Hope that
will be acceptable.
Other patches are new they:
- fix recursive fault in p2p target mode with st21nfca
- fix bad behavior on st21nfcb
- add ISO15693 technology for st21nfcb with a specific prioprietary
RF protocol value.
- fix st21nfcb dts documentation
Best Regards
Christophe
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: Replace all remaining IS_ERR(skb) with !skb
NFC: st21nfca: Fix potential double kfree_skb error
.../devicetree/bindings/net/nfc/st21nfcb.txt | 2 +-
drivers/nfc/st21nfca/st21nfca.c | 5 ++---
drivers/nfc/st21nfca/st21nfca_dep.c | 25 ++++++++++++----------
drivers/nfc/st21nfcb/i2c.c | 23 +++++---------------
drivers/nfc/st21nfcb/ndlc.c | 6 +++++-
drivers/nfc/st21nfcb/ndlc.h | 4 ++++
drivers/nfc/st21nfcb/st21nfcb.c | 11 ++++++++++
include/net/nfc/nci_core.h | 9 ++++----
net/nfc/nci/ntf.c | 9 +++++++-
9 files changed, 55 insertions(+), 39 deletions(-)
--
1.9.1
--
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
next reply other threads:[~2014-09-12 19:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 19:49 Christophe Ricard [this message]
[not found] ` <1410551381-7565-1-git-send-email-christophe-h.ricard-qxv4g6HH51o@public.gmane.org>
2014-09-12 19:49 ` [PATCH 01/11] NFC: st21nfca: Fix few coding style issue Christophe Ricard
2014-09-12 19:49 ` [PATCH 02/11] NFC: st21nfca: Fix potential skb leaks in NFC-DEP code Christophe Ricard
2014-09-12 19:49 ` [PATCH 03/11] NFC: st21nfca: Fix recursive fault when doing p2p in target mode Christophe Ricard
2014-09-12 19:49 ` [PATCH 04/11] NFC: dts: st21nfcb_i2c: Fix invalid interrupts polarity Christophe Ricard
2014-09-12 19:49 ` [PATCH 05/11] NFC: st21nfcb: Fix improper management of -EREMOTEIO error code Christophe Ricard
2014-09-12 19:49 ` [PATCH 06/11] NFC: st21nfcb: Fix improper ndlc T2 management Christophe Ricard
2014-09-12 19:49 ` [PATCH 07/11] NFC: nci: Add support for proprietary RF Protocols Christophe Ricard
2014-09-12 19:49 ` [PATCH 08/11] NFC: st21nfcb: Add ISO15693 Reader/Writer support Christophe Ricard
2014-09-12 19:49 ` [PATCH 09/11] NFC: st21nfcb: remove error output Christophe Ricard
2014-09-12 19:49 ` [PATCH 10/11] NFC: st21nfca: Replace all remaining IS_ERR(skb) with !skb Christophe Ricard
2014-09-12 19:49 ` [PATCH 11/11] NFC: st21nfca: Fix potential double kfree_skb error Christophe Ricard
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=1410551381-7565-1-git-send-email-christophe-h.ricard@st.com \
--to=christophe.ricard-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=christophe-h.ricard-qxv4g6HH51o@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nfc-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org \
--cc=sameo-VuQAYsv1563Yd54FQh9/CA@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 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.