From: Niklas Cassel <cassel@kernel.org>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Nishanth Menon" <nm@ti.com>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
"Tero Kristo" <kristo@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Siddharth Vadapalli" <s-vadapalli@ti.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Francesco Dolcini" <francesco.dolcini@toradex.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v1 0/2] PCI: ti: k3: Fix TI J721E PERST# polarity
Date: Fri, 12 Jul 2024 12:40:45 +0200 [thread overview]
Message-ID: <ZpEILZ2DLhvYYGci@ryzen.lan> (raw)
In-Reply-To: <ZpEGmeJUJxrDFQWa@ryzen.lan>
On Fri, Jul 12, 2024 at 12:34:01PM +0200, Niklas Cassel wrote:
>
> If you knew about it, I think that you should have stated that your are
> breaking DT compatibility in the commit message, while also explaining it
> is acceptable in your specific case.
s/while also explaining it is/while also explaining why it is/
next prev parent reply other threads:[~2024-07-12 10:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 10:00 [PATCH v1 0/2] PCI: ti: k3: Fix TI J721E PERST# polarity Francesco Dolcini
2024-07-03 10:00 ` [PATCH v1 1/2] arm64: dts: ti: Mark PCIe PERST# polarity active low in DT Francesco Dolcini
2024-07-03 10:00 ` [PATCH v1 2/2] PCI: j721e: Fix PERST# polarity Francesco Dolcini
2024-07-06 6:44 ` [PATCH v1 0/2] PCI: ti: k3: Fix TI J721E " Siddharth Vadapalli
2024-07-11 14:21 ` Niklas Cassel
2024-07-11 15:25 ` Francesco Dolcini
2024-07-12 10:34 ` Niklas Cassel
2024-07-12 10:40 ` Niklas Cassel [this message]
2024-08-06 14:35 ` Francesco Dolcini
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=ZpEILZ2DLhvYYGci@ryzen.lan \
--to=cassel@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=francesco.dolcini@toradex.com \
--cc=francesco@dolcini.it \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=vigneshr@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.