From: Johan Hovold <johan@kernel.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
cros-qcom-dts-watchers@chromium.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] arm64: dts: qcom: minor whitespace cleanup around '='
Date: Mon, 3 Jul 2023 12:06:31 +0200 [thread overview]
Message-ID: <ZKKdp8r5Z_47iU-j@hovoldconsulting.com> (raw)
In-Reply-To: <0f4f5a4d-379b-c00c-6bf2-58c08fcc4551@linaro.org>
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
next prev parent reply other threads:[~2023-07-03 10:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 18:50 [PATCH 1/2] arm64: dts: qcom: minor whitespace cleanup around '=' Krzysztof Kozlowski
2023-07-02 18:50 ` [PATCH 2/2] ARM: " Krzysztof Kozlowski
2023-07-03 9:31 ` Konrad Dybcio
2023-07-03 9:30 ` [PATCH 1/2] arm64: " Konrad Dybcio
2023-07-03 9:38 ` Johan Hovold
2023-07-03 9:56 ` Konrad Dybcio
2023-07-03 10:06 ` Johan Hovold [this message]
2023-07-03 16:08 ` Krzysztof Kozlowski
2023-07-03 16:09 ` Krzysztof Kozlowski
2023-07-10 5:07 ` (subset) " Bjorn Andersson
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=ZKKdp8r5Z_47iU-j@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox