From: Vinod Koul <vkoul@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
Nagarjuna Kristam <nkristam@nvidia.com>,
jonathanh@nvidia.com, mark.rutland@arm.com, robh+dt@kernel.org,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V4 0/7] Tegra XUSB charger detect support
Date: Fri, 17 Jul 2020 12:13:24 +0530 [thread overview]
Message-ID: <20200717064324.GJ82923@vkoul-mobl> (raw)
In-Reply-To: <20200716124809.GC535268@ulmo>
On 16-07-20, 14:48, Thierry Reding wrote:
> Hi Kishon, Vinod,
>
> did you have any further comments on this series or is it good to go
> into v5.9?
I dont have this series in my inbox, can you please rebase and resend
--
~Vinod
prev parent reply other threads:[~2020-07-17 6:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 10:18 [PATCH V4 0/7] Tegra XUSB charger detect support Nagarjuna Kristam
2020-06-26 10:18 ` [PATCH V4 1/7] dt-bindings: phy: tegra-xusb: Add charger-detect property Nagarjuna Kristam
2020-06-26 10:18 ` [PATCH V4 2/7] phy: tegra: xusb: Add support for UTMI pad power control Nagarjuna Kristam
2020-06-26 10:18 ` [PATCH V4 3/7] phy: tegra: xusb: Add USB2 pad power control support for Tegra210 Nagarjuna Kristam
2020-06-26 14:02 ` kernel test robot
2020-06-26 10:18 ` [PATCH V4 4/7] phy: tegra: xusb: Add soc ops API to enable UTMI PAD protection Nagarjuna Kristam
2020-06-26 10:19 ` [PATCH V4 5/7] phy: tegra: xusb: Add support for charger detect Nagarjuna Kristam
2020-06-26 10:19 ` [PATCH V4 6/7] phy: tegra: xusb: Enable charger detect for Tegra186 Nagarjuna Kristam
2020-06-26 10:19 ` [PATCH V4 7/7] phy: tegra: xusb: Enable charger detect for Tegra210 Nagarjuna Kristam
2020-07-16 12:48 ` [PATCH V4 0/7] Tegra XUSB charger detect support Thierry Reding
2020-07-17 6:43 ` Vinod Koul [this message]
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=20200717064324.GJ82923@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nkristam@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
/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