From: Thomas Gleixner <tglx@linutronix.de>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: linux-kernel@vger.kernel.org, yurovsky@gmail.com,
Jason Cooper <jason@lakedaemon.net>,
Marc Zyngier <marc.zyngier@arm.com>,
Shawn Guo <shawnguo@kernel.org>,
Tyler Baker <tyler.baker@linaro.org>
Subject: Re: [PATCH v2] drivers/irqchip: Enable IMX_GPCV2 on i.MX7 by default
Date: Fri, 14 Apr 2017 23:01:57 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1704142243470.2327@nanos> (raw)
In-Reply-To: <20170414202812.2329-1-andrew.smirnov@gmail.com>
On Fri, 14 Apr 2017, Andrey Smirnov wrote:
> i.MX7 has GPCv2 IP block and should be one of the main users of that
> driver. Unitl now, however, this driver was not being used by i.MX7
> code and GPCv2 block not specified in corresponding .dts(i). In light
> of the series [1] and problems that lack of the driver creates with it
> [2], enable this option when i.MX7 support is selected.
Please don't do this link dance. Explain in short precise words what this
is about. Links are only useful when there is information which is too big
to put into a change log or the mail thread contains useful context like a
sequence of steps which led to a patch.
In that case [1] links to a patch for a device tree blob. That's not really
useful to understand this patch. [2] is halfways useful, but you could
simply explain it directly.
Let me give you an example:
i.MX7 contains a GPCv2 IP block, but it was not enabled so far because
the required device tree parts are missing and no other code depends on
it.
The device tree parts and actual users are on the way to mainline, so
it's required to select the GPCv2 driver for i.MX7.
That nicely gives the context (Paragraph 1) and the reason (P 2).
But, this patch is actually wrong. If the SoC or other code parts depend on
it then these parts should simply add a
select IMX_GPCV2
statement to the relevant Kconfig. That avoids endless
default y if FOO || (BLA && !MEH) || BRR .....
lines and enforces the enablement when the actual user is selected.
> [1] https://lkml.org/lkml/2017/4/13/327
> [2] https://lkml.org/lkml/2017/4/13/646
Please do not use lkml.org references. If you ever want to link to a mail
thread then please use http://lkml.kernel.org/r/$Message-Id. That is a
redirector to a known to be available mail archive.
Thanks,
tglx
next prev parent reply other threads:[~2017-04-14 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 20:28 Andrey Smirnov
2017-04-14 21:01 ` Thomas Gleixner [this message]
2017-04-14 21:24 ` Andrey Smirnov
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=alpine.DEB.2.20.1704142243470.2327@nanos \
--to=tglx@linutronix.de \
--cc=andrew.smirnov@gmail.com \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=shawnguo@kernel.org \
--cc=tyler.baker@linaro.org \
--cc=yurovsky@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®