From: Jason Cooper <jason@lakedaemon.net>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: Silvio Fricke <silvio.fricke@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 0/3] removing of some unused/unsupported dts entries
Date: Sat, 13 Dec 2014 09:33:28 -0500 [thread overview]
Message-ID: <20141213143328.GA967@titan.lakedaemon.net> (raw)
In-Reply-To: <8761dfgb1o.fsf@why.wild-wind.fr.eu.org>
Silvio, Marc,
On Sat, Dec 13, 2014 at 09:21:23AM +0000, Marc Zyngier wrote:
> On Sat, Dec 13 2014 at 1:46:45 am GMT, Silvio Fricke <silvio.fricke@gmail.com> wrote:
>
> Hi Silvio,
>
> > I have found some dts entries which are not evaluated by the drivers. This
> > patch remove this entries from the dts files.
> > Jason has mentioned I should CC: Thomas, Marc and him self to this
> > mails.
>
> As far as I can tell, this looks correct. A few key things though:
>
> - Please write decent commit logs. Indicate *why* you think these
> properties can be removed (hint: not finding corresponding in the
> drivers is not enough a reason, the binding itself matters).
Right. The real issue is the state of these properties within the
binding documentation. Linux isn't the only consumer of these dts
files (*BSD, barebox, etc), so us not using them doesn't necessarily
mean the property should be removed.
The most important lesson (recently learned ;-) ) is to make sure all
properties are accurately describing the *hardware*. Not Linux's
implementation of talking to the hardware. That'll go a long way if the
changelog discusses how property X is an implementation detail vice a
hardware characteristic or feature.
> - Cc the relevant platform maintainers. You're changing things that they
> care about, basic courtesy is to keep them in the loop.
True. In Silvio's defense, I just told him to Cc us to get the ball
rolling. (I tend to dislike long discussions on chat mediums, I'd much
rather they be in email. So I was definitely too succinct).
For the record, you can use ./scripts/get_maintainer.pl on your patches
to make sure you get most of the right people. In this case, that'll
include the DT maintainers. You may want to run a get_maintainer.pl -f
arch/arm/mach-$ARCH for each of the dts file you touch. Those
maintainers usually wrangle the patches for their dts files.
Unfortunately, not all of them have updated MAINTAINERS
(<cough>mvebu<cough>) to include the dts file patterns.
thx,
Jason.
prev parent reply other threads:[~2014-12-13 14:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-13 1:46 [PATCH 0/3] removing of some unused/unsupported dts entries Silvio Fricke
2014-12-13 1:46 ` [PATCH 1/3] ARM: mx5: dts: remove unused irq-trigger entry Silvio Fricke
2014-12-13 1:46 ` [PATCH 2/3] ARM: tegra: " Silvio Fricke
2014-12-13 1:46 ` [PATCH 3/3] ARM: SPEAr: dts: remove unused irq-trigger, id and block entries Silvio Fricke
2014-12-15 4:09 ` Viresh Kumar
2014-12-13 9:21 ` [PATCH 0/3] removing of some unused/unsupported dts entries Marc Zyngier
2014-12-13 14:33 ` Jason Cooper [this message]
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=20141213143328.GA967@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=silvio.fricke@gmail.com \
--cc=tglx@linutronix.de \
/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