From: David Miller <davem@davemloft.net>
To: poeschel@lemonage.de
Cc: swinslow@gmail.com, tglx@linutronix.de,
kstewart@linuxfoundation.org, allison@lohutok.net,
opensource@jilayne.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, johan@kernel.org,
horms@verge.net.au
Subject: Re: [PATCH v8 1/7] nfc: pn533: i2c: "pn532" as dt compatible string
Date: Thu, 19 Sep 2019 13:32:50 +0200 (CEST) [thread overview]
Message-ID: <20190919.133250.1851009450153650293.davem@davemloft.net> (raw)
In-Reply-To: <20190919091645.16439-1-poeschel@lemonage.de>
As we are in the merge window, the net-next tree is closed, as shown
also at:
http://vger.kernel.org/~davem/net-next.html
Please resubmit this after the merge window when the net-next tree opens
back up.
Please also provide an appropriate "[PATCH 0/N]" header posting
explaining what the patch series is doing, how it is doing it, and
why it is doing it that way.
Thank you.
prev parent reply other threads:[~2019-09-19 11:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 9:16 [PATCH v8 1/7] nfc: pn533: i2c: "pn532" as dt compatible string Lars Poeschel
2019-09-19 9:16 ` [PATCH v8 2/7] nfc: pn532: Add uart phy docs and rename it Lars Poeschel
2019-09-27 15:52 ` Rob Herring
2019-09-30 7:47 ` Lars Poeschel
2019-09-19 9:16 ` [PATCH v8 3/7] nfc: pn533: Add dev_up/dev_down hooks to phy_ops Lars Poeschel
2019-09-19 9:16 ` [PATCH v8 4/7] nfc: pn533: Split pn533 init & nfc_register Lars Poeschel
2019-09-19 9:16 ` [PATCH v8 5/7] nfc: pn533: add UART phy driver Lars Poeschel
2019-09-19 9:16 ` [PATCH v8 6/7] nfc: pn533: Add autopoll capability Lars Poeschel
2019-09-19 9:16 ` [PATCH v8 7/7] nfc: pn532_uart: Make use of pn532 autopoll Lars Poeschel
2019-09-19 11:32 ` David Miller [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=20190919.133250.1851009450153650293.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=allison@lohutok.net \
--cc=horms@verge.net.au \
--cc=johan@kernel.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=opensource@jilayne.com \
--cc=poeschel@lemonage.de \
--cc=swinslow@gmail.com \
--cc=tglx@linutronix.de \
/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).