From: Lars Poeschel <poeschel@lemonage.de>
To: Johan Hovold <johan@kernel.org>
Cc: devicetree@vger.kernel.org, Samuel Ortiz <sameo@linux.intel.com>,
"open list:NFC SUBSYSTEM" <linux-wireless@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: [PING 2] [PATCH v5 1/7] nfc: pn533: i2c: "pn532" as dt compatible string
Date: Mon, 12 Aug 2019 09:40:49 +0200 [thread overview]
Message-ID: <20190812074035.GA9797@lem-wkst-02.lemonage> (raw)
In-Reply-To: <20190805124236.GG3574@localhost>
On Mon, Aug 05, 2019 at 02:42:36PM +0200, Johan Hovold wrote:
> You may want to resend this series to netdev now. David Miller will be
> picking up NFC patches directly from there.
Thank you very much for this information. Johannes Berg did reach out to
me already.
Rebase, test and resend is queued up for one of my next free timeslots.
Thanks again,
Lars
prev parent reply other threads:[~2019-08-12 7:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 16:18 [PATCH v5 1/7] nfc: pn533: i2c: "pn532" as dt compatible string Lars Poeschel
2019-01-11 16:18 ` [PATCH v5 2/7] nfc: pn532_uart: Add NXP PN532 to devicetree docs Lars Poeschel
2019-01-15 19:59 ` Rob Herring
2019-01-24 10:02 ` Lars Poeschel
2019-01-11 16:18 ` [PATCH v5 3/7] nfc: pn533: Add dev_up/dev_down hooks to phy_ops Lars Poeschel
2019-01-11 16:18 ` [PATCH v5 4/7] nfc: pn533: Split pn533 init & nfc_register Lars Poeschel
2019-01-11 16:18 ` [PATCH v5 5/7] nfc: pn533: add UART phy driver Lars Poeschel
2019-01-11 16:18 ` [PATCH v5 6/7] nfc: pn533: Add autopoll capability Lars Poeschel
2019-01-11 16:18 ` [PATCH v5 7/7] nfc: pn532_uart: Make use of pn532 autopoll Lars Poeschel
2019-02-28 10:48 ` [PING] [PATCH v5 1/7] nfc: pn533: i2c: "pn532" as dt compatible string Lars Poeschel
2019-04-03 9:47 ` [PING 2] " Lars Poeschel
2019-08-05 12:42 ` Johan Hovold
2019-08-12 7:40 ` Lars Poeschel [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=20190812074035.GA9797@lem-wkst-02.lemonage \
--to=poeschel@lemonage.de \
--cc=devicetree@vger.kernel.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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).