netdev - Re: [PATCH v11 0/7] nfc: pn533: add uart phy driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20191029.211158.1584843573342050158.davem@davemloft.net>
Date:   Tue, 29 Oct 2019 21:11:58 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     poeschel@...onage.de
Cc:     kstewart@...uxfoundation.org, tglx@...utronix.de,
        opensource@...ayne.com, gregkh@...uxfoundation.org,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        robh+dt@...nel.org, mark.rutland@....com,
        devicetree@...r.kernel.org, swinslow@...il.com,
        gustavo@...eddedor.com, keescook@...omium.org, allison@...utok.net,
        johan@...nel.org, horms@...ge.net.au
Subject: Re: [PATCH v11 0/7] nfc: pn533: add uart phy driver

From: Lars Poeschel <poeschel@...onage.de>
Date: Tue, 29 Oct 2019 15:43:13 +0100

> 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.
> In v11 of this patchseries I address a byte ordering issue reported
> by kbuild test robot in patch 5/7.

Series applied to net-next.