From: Pengyu Luo <mitltlatltl@gmail.com>
To: konrad.dybcio@oss.qualcomm.com
Cc: andersson@kernel.org, bryan.odonoghue@linaro.org,
conor+dt@kernel.org, devicetree@vger.kernel.org,
hdegoede@redhat.com, ilpo.jarvinen@linux.intel.com,
jdelvare@suse.com, konradybcio@kernel.org, krzk+dt@kernel.org,
krzk@kernel.org, linux-arm-msm@vger.kernel.org,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@roeck-us.net, mitltlatltl@gmail.com,
platform-driver-x86@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH RESEND v6 0/3] platform: arm64: Huawei Matebook E Go embedded controller
Date: Sun, 2 Feb 2025 00:34:13 +0800 [thread overview]
Message-ID: <20250201163416.2774-1-mitltlatltl@gmail.com> (raw)
In-Reply-To: <018281e0-001a-4587-b775-a9df6e54f75e@oss.qualcomm.com>
On Sat, Feb 1, 2025 at 11:35 PM Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> wrote:
> On 1.02.2025 8:38 AM, Pengyu Luo wrote:
> > On Sat, Feb 1, 2025 at 5:20 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
> >> On 31/01/2025 10:21, Pengyu Luo wrote:
> >>> This adds binding, drivers and the DT support for the Huawei Matebook E Go
> >>> (sc8280xp-based) Embedded Controller which is also found in Huawei Matebook
> >>> E Go LTE (sc8180x-based), but I don't have the sc8180x one to perform
> >>> tests, so this series enable support for sc8280xp variant only, this series
> >>> provides the following features:
> >>>
> >>> - battery and charger information report
> >>> - charging thresholds control
> >>> - FN lock (An alternative method)
> >>> - LID switch detection
> >>> - Temperature sensors
> >>> - USB Type-C altmode
> >>> - USB Type-C PD(high power)
> >>>
> >>
> >> Why are you resending?
> >>
> >> Previous version was only week ago and minimal time is two weeks. Plus
> >> its merge window, so this resend is unjustified.
> >
> > Sorry, I am still new to the process, I may have misunderstood something.
> > I sent it because I had got at leaset one reviewed tag for every patch
> > from the corresponding subsystem maintainer. Can I expect that there would
> > be no reviewing? All I need to do is wait for it to be applied.
>
> Generally if people have a concern, they'll share it with you.
> It may be that one review is not enough, this is up to the maintainer.
>
> You don't need to resend after you get new tags, the maintainer tools will
> pick those up when the patches are being applied.
>
> Patches are generally not picked up by maintainers in the timeframe between
> stable vX.Y release and vX.(Y+1)-rc1, this is the time when Linus accepts
> code that has been sitting in the maintainers' branches for some time and
> getting build/functionality tested in linux-next over the previous cycle
>
It is helpful, thanks for explanation.
Best wishes,
Pengyu
next prev parent reply other threads:[~2025-02-01 16:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 9:21 [PATCH RESEND v6 0/3] platform: arm64: Huawei Matebook E Go embedded controller Pengyu Luo
2025-01-31 9:21 ` [PATCH RESEND v6 1/3] dt-bindings: platform: Add Huawei Matebook E Go EC Pengyu Luo
2025-01-31 9:21 ` [PATCH RESEND v6 2/3] platform: arm64: add Huawei Matebook E Go EC driver Pengyu Luo
2025-01-31 20:07 ` kernel test robot
2025-01-31 9:21 ` [PATCH RESEND v6 3/3] arm64: dts: qcom: gaokun3: Add Embedded Controller node Pengyu Luo
2025-01-31 21:20 ` [PATCH RESEND v6 0/3] platform: arm64: Huawei Matebook E Go embedded controller Krzysztof Kozlowski
2025-02-01 7:38 ` Pengyu Luo
2025-02-01 15:34 ` Konrad Dybcio
2025-02-01 16:34 ` Pengyu Luo [this message]
2025-02-02 14:19 ` Krzysztof Kozlowski
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=20250201163416.2774-1-mitltlatltl@gmail.com \
--to=mitltlatltl@gmail.com \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jdelvare@suse.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=platform-driver-x86@vger.kernel.org \
--cc=robh@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).