linux-kernel - Re: [PATCH 1/2] arm64: dts: qcom: minor whitespace cleanup around '='

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <ZKKdp8r5Z_47iU-j@hovoldconsulting.com>
Date:   Mon, 3 Jul 2023 12:06:31 +0200
From:   Johan Hovold <johan@...nel.org>
To:     Konrad Dybcio <konrad.dybcio@...aro.org>
Cc:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        Andy Gross <agross@...nel.org>,
        Bjorn Andersson <andersson@...nel.org>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Conor Dooley <conor+dt@...nel.org>,
        cros-qcom-dts-watchers@...omium.org, linux-arm-msm@...r.kernel.org,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] arm64: dts: qcom: minor whitespace cleanup around '='

On Mon, Jul 03, 2023 at 11:56:40AM +0200, Konrad Dybcio wrote:
> On 3.07.2023 11:38, Johan Hovold wrote:
 
> > Konrad, please remember to trim irrelevant context from your replies
> > (e.g. so that we don't have to skim through thousands of lines to find
> > a single comment).
> My actual reply begins at line 77, which is considerably less than
> thousands and is concluded by my signoff, which signifies the end
> of the message.

That was not the point. The point is that you should trim your replies,
including context after your reply (sure, some people keep context when
providing reviewed-by tags, but generally replies should be trimmed).

Including an empty line before your inline comments would also make your
replies easier to read.

Johan