From: ChiYuan Huang <cy_huang@richtek.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: <broonie@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>, <robh+dt@kernel.org>,
<lgirdwood@gmail.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] Add compatible support for RT5733
Date: Mon, 10 Jul 2023 15:09:56 +0800 [thread overview]
Message-ID: <20230710070956.GA31191@linuxcarl2.richtek.com> (raw)
In-Reply-To: <224afbe7-f0d5-ced2-a300-9e05789f08e8@linaro.org>
On Mon, Jul 10, 2023 at 08:55:17AM +0200, Krzysztof Kozlowski wrote:
> On 10/07/2023 03:47, ChiYuan Huang wrote:
> > On Thu, Jun 29, 2023 at 10:29:54PM +0800, cy_huang@richtek.com wrote:
> > Hi,
> >> From: ChiYuan Huang <cy_huang@richtek.com>
> >>
> >> This series is to add the compatible support for rt5733 based on rt5739.
> >>
> > Sorry, not intend to ping, just want to check the current review status.
> >
> > Any comment about this patch series?
>
> You sent it during merge window, so what do you expect? What should
> happen during the merge window?
>
Since I do not know it's merge windows period, sorry to bother you guys.
Thanks for the notice.
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2023-07-10 7:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 14:29 [PATCH v2 0/2] Add compatible support for RT5733 cy_huang
2023-06-29 14:29 ` [PATCH v2 1/2] regulator: dt-bindings: rt5739: Add compatible for rt5733 cy_huang
2023-06-29 14:29 ` [PATCH v2 2/2] regulator: rt5739: Add DID check and " cy_huang
2023-07-10 1:47 ` [PATCH v2 0/2] Add compatible support for RT5733 ChiYuan Huang
2023-07-10 6:55 ` Krzysztof Kozlowski
2023-07-10 7:09 ` ChiYuan Huang [this message]
2023-07-10 7:27 ` Krzysztof Kozlowski
2023-07-12 14:29 ` Mark Brown
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=20230710070956.GA31191@linuxcarl2.richtek.com \
--to=cy_huang@richtek.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.