linux-kernel - Re: [PATCH RESEND v6 0/3] platform: arm64: Huawei Matebook E Go embedded controller

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250201163416.2774-1-mitltlatltl@gmail.com>
Date: Sun,  2 Feb 2025 00:34:13 +0800
From: Pengyu Luo <mitltlatltl@...il.com>
To: konrad.dybcio@....qualcomm.com
Cc: andersson@...nel.org,
	bryan.odonoghue@...aro.org,
	conor+dt@...nel.org,
	devicetree@...r.kernel.org,
	hdegoede@...hat.com,
	ilpo.jarvinen@...ux.intel.com,
	jdelvare@...e.com,
	konradybcio@...nel.org,
	krzk+dt@...nel.org,
	krzk@...nel.org,
	linux-arm-msm@...r.kernel.org,
	linux-hwmon@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	linux@...ck-us.net,
	mitltlatltl@...il.com,
	platform-driver-x86@...r.kernel.org,
	robh@...nel.org
Subject: Re: [PATCH RESEND v6 0/3] platform: arm64: Huawei Matebook E Go embedded controller

On Sat, Feb 1, 2025 at 11:35 PM Konrad Dybcio <konrad.dybcio@....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@...nel.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