From: Bongsu Jeon <bongsu.jeon2@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-nfc@lists.01.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Bongsu Jeon <bongsu.jeon@samsung.com>
Subject: Re: [PATCH v5 net-next 1/4] dt-bindings: net: nfc: s3fwrn5: Support a UART interface
Date: Thu, 3 Dec 2020 07:16:38 +0900 [thread overview]
Message-ID: <CACwDmQD8dFCd2u=BnL8VrzQ=NuPYA9z44uBJsKSaUN5yR4R8Mw@mail.gmail.com> (raw)
In-Reply-To: <20201202171638.GA2778@kozik-lap>
On Thu, Dec 3, 2020 at 2:16 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>
> On Wed, Dec 02, 2020 at 08:47:38PM +0900, Bongsu Jeon wrote:
> > From: Bongsu Jeon <bongsu.jeon@samsung.com>
> >
> > Since S3FWRN82 NFC Chip, The UART interface can be used.
> > S3FWRN82 supports I2C and UART interface.
> >
> > Signed-off-by: Bongsu Jeon <bongsu.jeon@samsung.com>
> > ---
> > .../bindings/net/nfc/samsung,s3fwrn5.yaml | 31 +++++++++++++++++++---
> > 1 file changed, 28 insertions(+), 3 deletions(-)
> >
>
> Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
>
> Best regards,
> Krzysztof
Thanks a lot for advising and reviewing my patches.
next prev parent reply other threads:[~2020-12-02 22:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 11:47 [PATCH v5 net-next 0/4] nfc: s3fwrn5: Support a UART interface Bongsu Jeon
2020-12-02 11:47 ` [PATCH v5 net-next 1/4] dt-bindings: net: " Bongsu Jeon
2020-12-02 17:16 ` Krzysztof Kozlowski
2020-12-02 22:16 ` Bongsu Jeon [this message]
2020-12-02 11:47 ` [PATCH v5 net-next 2/4] nfc: s3fwrn5: reduce the EN_WAIT_TIME Bongsu Jeon
2020-12-02 11:47 ` [PATCH v5 net-next 3/4] nfc: s3fwrn5: extract the common phy blocks Bongsu Jeon
2020-12-02 11:47 ` [PATCH v5 net-next 4/4] nfc: s3fwrn5: Support a UART interface Bongsu Jeon
2020-12-03 1:58 ` [PATCH v5 net-next 0/4] " Jakub Kicinski
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='CACwDmQD8dFCd2u=BnL8VrzQ=NuPYA9z44uBJsKSaUN5yR4R8Mw@mail.gmail.com' \
--to=bongsu.jeon2@gmail.com \
--cc=bongsu.jeon@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfc@lists.01.org \
--cc=netdev@vger.kernel.org \
/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).