All of lore.kernel.org
 help / color / mirror / Atom feed
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 00/10] Secure Element support for HCI based NFC controller & st21nfca integration
Date: Tue, 27 Jan 2015 23:45:58 +0100	[thread overview]
Message-ID: <20150127224558.GA32667@ribalta.mp.intel.com> (raw)
In-Reply-To: <1422317900-3810-1-git-send-email-christophe-h.ricard-qxv4g6HH51o@public.gmane.org>

On Tue, Jan 27, 2015 at 01:18:10AM +0100, Christophe Ricard wrote:
> Christophe Ricard (10):
>   NFC: hci: Change event_received handler gate parameter to pipe
>   NFC: hci: Add pipes table to reference them with a tuple {gate, host}
>   NFC: hci: Change nfc_hci_send_response gate parameter to pipe
>   NFC: hci: Reference every pipe information according to notification
>   NFC: hci: Add cmd_received handler
>   NFC: pn544: Change event_received gate parameter to pipe
>   NFC: microread: Change event_received gate parameter to pipe
>   NFC: hci: Remove nfc_hci_pipe2gate function
>   NFC: st21nfca: Adding support for secure element
>   NFC: dts: st21nfca: Document ese-present & uicc-present DTS property
All 10 patches applied, with some commit messages fixes.
Thanks a lot.

Cheers,
Samuel.
--
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

      parent reply	other threads:[~2015-01-27 22:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27  0:18 [PATCH 00/10] Secure Element support for HCI based NFC controller & st21nfca integration Christophe Ricard
     [not found] ` <1422317900-3810-1-git-send-email-christophe-h.ricard-qxv4g6HH51o@public.gmane.org>
2015-01-27  0:18   ` [PATCH 01/10] NFC: hci: Change event_received handler gate parameter to pipe Christophe Ricard
2015-01-27  0:18   ` [PATCH 02/10] NFC: hci: Add pipes table to reference them with a tuple {gate, host} Christophe Ricard
2015-01-27  0:18   ` [PATCH 03/10] NFC: hci: Change nfc_hci_send_response gate parameter to pipe Christophe Ricard
2015-01-27  0:18   ` [PATCH 04/10] NFC: hci: Reference every pipe information according to notification Christophe Ricard
2015-01-27  0:18   ` [PATCH 05/10] NFC: hci: Add cmd_received handler Christophe Ricard
2015-01-27  0:18   ` [PATCH 06/10] NFC: pn544: Change event_received gate parameter to pipe Christophe Ricard
2015-01-27  0:18   ` [PATCH 07/10] NFC: microread: " Christophe Ricard
2015-01-27  0:18   ` [PATCH 08/10] NFC: hci: Remove nfc_hci_pipe2gate function Christophe Ricard
2015-01-27  0:18   ` [PATCH 09/10] NFC: st21nfca: Adding support for secure element Christophe Ricard
2015-01-27  0:18   ` [PATCH 10/10] NFC: dts: st21nfca: Document ese-present & uicc-present DTS property Christophe Ricard
2015-01-27 22:45   ` 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=20150127224558.GA32667@ribalta.mp.intel.com \
    --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 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.