On 12/5/25 2:45 PM, David Heidelberg wrote:
> On 05/12/2025 14:27, Konrad Dybcio wrote:
>
> [...]
>
>>> @@ -637,3 +643,4 @@ &wifi {
>>> vdd-3.3-ch0-supply = <&vreg_l25a_3p3>;
>>> vdd-3.3-ch1-supply = <&vreg_l23a_3p3>;
>>> };
>>> +
>>>
>>
>> Stray hunk?
>
> I think your comment goes into the category of "extreme nitpicks".
>
> Here as usual I guess there are three options:
> - another revision because of newline
> - maintainer merge it with it and nothing happens
> - while merge, maintainer remove the line
$ LC_ALL=C b4 shazam [email protected] -P 1
Grabbing thread from
lore.kernel.org/all/[email protected]/t.mbox.gz
Checking for newer revisions
Grabbing search results from lore.kernel.org
Analyzing 6 messages in the thread
Analyzing 0 code-review messages
Checking attestation on all messages, may take a moment...
---
[PATCH v2 1/3] arm64: dts: qcom: sdm845-xiaomi-beryllium: Enable SLPI
---
✗ No key: openpgp/[email protected]
---
Total patches: 1 (cherrypicked: 1)
---
Base: using specified base-commit 6987d58a9cbc5bd57c983baa514474a86c945d56
Applying: arm64: dts: qcom: sdm845-xiaomi-beryllium: Enable SLPI
/<snip path>/.git/rebase-apply/patch:26: new blank line at EOF.
+
warning: 1 line adds whitespace errors.
It works best when both submitters and maintainers check their work..
Konrad
