Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Thu, 19 Sep 2019 13:32:50 +0200 (CEST)
Message-Id: <20190919.133250.1851009450153650293.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
From:   David Miller <davem@davemloft.net>
In-Reply-To: <20190919091645.16439-1-poeschel@lemonage.de>
References: <20190919091645.16439-1-poeschel@lemonage.de>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


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.