From: Johan Hovold <johan@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Johan Hovold <johan+linaro@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Alessandro Zummo <a.zummo@towertech.it>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-rtc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: rtc: qcom-pm8xxx: fix inconsistent example
Date: Fri, 1 Dec 2023 17:37:33 +0100 [thread overview]
Message-ID: <ZWoLzTX0zmCOxsVm@hovoldconsulting.com> (raw)
In-Reply-To: <20231201-pursuable-endocrine-1318f4843597@spud>
[-- Attachment #1: Type: text/plain, Size: 679 bytes --]
On Fri, Dec 01, 2023 at 04:27:33PM +0000, Conor Dooley wrote:
> On Fri, Dec 01, 2023 at 10:31:22AM +0100, Johan Hovold wrote:
> > A Fixes tag does not in itself imply that something should be
> > backported, we have CC-stable tags for that.
>
> IDK, I think at this point every highly active kernel developer should
> be aware that the stable maintainers backport way more than just what
> gets explicitly CCed to stable.
I'm quite aware of that, and if one of my patches with a Fixes tag is
picked up for backporting when it should not I complain loudly.
For this patch, I would not necessarily complain however as the current
example is misleading.
Johan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-12-01 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 17:32 [PATCH] dt-bindings: rtc: qcom-pm8xxx: fix inconsistent example Johan Hovold
2023-12-01 8:32 ` Krzysztof Kozlowski
2023-12-01 9:31 ` Johan Hovold
2023-12-01 16:27 ` Conor Dooley
2023-12-01 16:37 ` Johan Hovold [this message]
2023-12-19 15:57 ` Johan Hovold
2024-01-08 0:32 ` Alexandre Belloni
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=ZWoLzTX0zmCOxsVm@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=a.zummo@towertech.it \
--cc=agross@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan+linaro@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=linux-rtc@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