From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 23233ECE58E for ; Tue, 15 Oct 2019 09:54:32 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 02C6321848 for ; Tue, 15 Oct 2019 09:54:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727429AbfJOJy3 (ORCPT ); Tue, 15 Oct 2019 05:54:29 -0400 Received: from smtp3.goneo.de ([85.220.129.37]:51302 "EHLO smtp3.goneo.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725890AbfJOJy2 (ORCPT ); Tue, 15 Oct 2019 05:54:28 -0400 Received: from localhost (localhost [127.0.0.1]) by smtp3.goneo.de (Postfix) with ESMTP id B639723F83E; Tue, 15 Oct 2019 11:54:25 +0200 (CEST) X-Virus-Scanned: by goneo Received: from smtp3.goneo.de ([127.0.0.1]) by localhost (smtp3.goneo.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tdP6agb7XihY; Tue, 15 Oct 2019 11:54:24 +0200 (CEST) Received: from lem-wkst-02.lemonage (hq.lemonage.de [87.138.178.34]) by smtp3.goneo.de (Postfix) with ESMTPSA id BCF4B23F80C; Tue, 15 Oct 2019 11:54:22 +0200 (CEST) Date: Tue, 15 Oct 2019 11:54:21 +0200 From: Lars Poeschel To: Jakub Kicinski Cc: Kate Stewart , Thomas Gleixner , Jilayne Lovejoy , Greg Kroah-Hartman , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, "David S. Miller" , Rob Herring , Mark Rutland , devicetree@vger.kernel.org, Steve Winslow , "Gustavo A. R. Silva" , Kees Cook , Allison Randal , Johan Hovold , Simon Horman Subject: Re: [PATCH v9 0/7] nfc: pn533: add uart phy driver Message-ID: <20191015095421.GB17778@lem-wkst-02.lemonage> References: <20191008140544.17112-1-poeschel@lemonage.de> <20191009172907.2f0877f4@cakuba.netronome.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191009172907.2f0877f4@cakuba.netronome.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Wed, Oct 09, 2019 at 05:29:07PM -0700, Jakub Kicinski wrote: > On Tue, 8 Oct 2019 16:05:37 +0200, Lars Poeschel wrote: > > The purpose of this patch series is to add a uart phy driver to the > > pn533 nfc driver. > > It first changes the dt strings and docs. The dt compatible strings > > need to change, because I would add "pn532-uart" to the already > > existing "pn533-i2c" one. These two are now unified into just > > "pn532". Then the neccessary changes to the pn533 core driver are > > made. Then the uart phy is added. > > As the pn532 chip supports a autopoll, I wanted to use this instead > > of the software poll loop in the pn533 core driver. It is added and > > activated by the last to patches. > > The way to add the autopoll later in seperate patches is chosen, to > > show, that the uart phy driver can also work with the software poll > > loop, if someone needs that for some reason. > > This patchset is already rebased on Johans "NFC: pn533: fix > > use-after-free and memleaks" patch > > https://lore.kernel.org/netdev/20191007164059.5927-1-johan@kernel.org/ > > as they would conflict. > > If for some reason Johans patch will not get merged, I can of course > > provide the patchset without depending on this patch. > > The memleak patch was a fix and it's on its way to the current 5.4-rc > releases - therefore it was merged into the net tree. Your set adds > support for a new bus, and will go into the net-next tree. > > It'd be best if you reposted once the net tree was merged into the > net-next tree (which usually happens every week or two). If you'd > rather not wait you need to rebase on top of the current net-next tree, > and maintainers will handle the conflicts. Thank you very much for this valueable information. I will repost the v10 of this patchset rebased on net-next, when the fix is appears there.