From: "Stanley Chang[昌育德]" <stanley_chang@realtek.com>
To: Oliver Neukum <oneukum@suse.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
Flavio Suligoi <f.suligoi@asem.it>, Roy Luo <royluo@google.com>,
Bagas Sanjaya <bagasdotme@gmail.com>, Ray Chi <raychi@google.com>,
"linux-phy@lists.infradead.org" <linux-phy@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: RE: [PATCH v9 2/5] phy: realtek: usb: Add driver for the Realtek SoC USB 2.0 PHY
Date: Thu, 27 Jul 2023 01:56:40 +0000 [thread overview]
Message-ID: <708d5e38c8f84aa995a16c8a018be40c@realtek.com> (raw)
In-Reply-To: <a11f0ec8-7eaa-aa3e-8b86-555e5dbe6e3e@suse.com>
Hi Oliver,
> nvmem_cell_read() can take NULL as the second argument.
> You are throwing away buf_size anyway.
>
Thanks for your suggestion.
Thanks,
Stanley
next prev parent reply other threads:[~2023-07-27 1:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 3:31 [PATCH v9 1/5] usb: phy: add usb phy notify port status API Stanley Chang
2023-07-25 3:31 ` [PATCH v9 2/5] phy: realtek: usb: Add driver for the Realtek SoC USB 2.0 PHY Stanley Chang
2023-07-26 8:13 ` Oliver Neukum
2023-07-27 1:56 ` Stanley Chang[昌育德] [this message]
2023-07-25 3:31 ` [PATCH v9 3/5] phy: realtek: usb: Add driver for the Realtek SoC USB 3.0 PHY Stanley Chang
2023-07-25 3:31 ` [PATCH v9 4/5] dt-bindings: phy: realtek: Add Realtek DHC RTD SoC USB 2.0 PHY Stanley Chang
2023-07-25 3:31 ` [PATCH v9 5/5] dt-bindings: phy: realtek: Add Realtek DHC RTD SoC USB 3.0 PHY Stanley Chang
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=708d5e38c8f84aa995a16c8a018be40c@realtek.com \
--to=stanley_chang@realtek.com \
--cc=bagasdotme@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=f.suligoi@asem.it \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=raychi@google.com \
--cc=robh+dt@kernel.org \
--cc=royluo@google.com \
--cc=stern@rowland.harvard.edu \
--cc=vkoul@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).