From: German Rivera <German.Rivera@freescale.com>
To: Alexander Graf <agraf@suse.de>, <gregkh@linuxfoundation.org>,
<arnd@arndb.de>, <linux-kernel@vger.kernel.org>
Cc: <stuart.yoder@freescale.com>, <Kim.Phillips@freescale.com>,
<scottwood@freescale.com>, <bhamciu1@freescale.com>,
<R89243@freescale.com>, <Geoff.Thorpe@freescale.com>,
<bhupesh.sharma@freescale.com>, <nir.erez@freescale.com>,
<richard.schmitt@freescale.com>
Subject: Re: [PATCH 2/3 v3] drivers/bus: Freescale Management Complex (fsl-mc) bus driver
Date: Tue, 11 Nov 2014 20:01:49 -0600 [thread overview]
Message-ID: <5462BF8D.2090805@freescale.com> (raw)
In-Reply-To: <545B7C9A.8000309@suse.de>
On 11/06/2014 07:50 AM, Alexander Graf wrote:
>
[cut]
>> +++ b/drivers/bus/fsl-mc/Kconfig
>> @@ -0,0 +1,13 @@
>> +#
>> +# Freescale Management Complex (MC) bus drivers
>> +#
>> +# Copyright (C) 2014 Freescale Semiconductor, Inc.
>> +#
>> +# This file is released under the GPLv2
>> +#
>> +
>> +config FSL_MC_BUS
>> + tristate "Freescale Management Complex (MC) bus driver"
>> + help
>> + Driver to enable the bus infrastructure for the Freescale
>> + QorIQ Management Complex.
>
> Isn't this missing some scope limitations? Should we really have the
> driver enabled on x86 for example?
>
I will add depends on OF && ARM64
> I would also make this slightly more verbose. People don't necessarily
> know what the QorIQ Management Complex is. Give people some idea what
> they're dealing with and preferably tell them hints that guide them from
> "SoC name" to "should I enable this option?".
>
> Also, usually the help text gives some guidance on what to do with the
> option if you're not sure. In this case, I would say advise the user to
> say N.
>
Will do.
>
> Alex
>
next prev parent reply other threads:[~2014-11-12 2:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-04 13:23 [PATCH 0/3 v3] drivers/bus: Freescale Management Complex bus driver patch series J. German Rivera
2014-10-04 13:23 ` [PATCH 1/3 v3] drivers/bus: Added Freescale Management Complex APIs J. German Rivera
2014-11-06 13:49 ` Alexander Graf
2014-11-12 0:49 ` German Rivera
2014-10-04 13:23 ` [PATCH 2/3 v3] drivers/bus: Freescale Management Complex (fsl-mc) bus driver J. German Rivera
2014-11-06 13:50 ` Alexander Graf
2014-11-12 2:01 ` German Rivera [this message]
2014-10-04 13:23 ` [PATCH 3/3 v3] drivers/bus: Device driver for FSL-MC DPRC devices J. German Rivera
2014-10-05 14:53 ` Timur Tabi
2014-10-06 14:48 ` German Rivera
2014-11-10 4:37 ` Timur Tabi
2014-11-06 13:51 ` Alexander Graf
2014-11-13 17:37 ` German Rivera
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=5462BF8D.2090805@freescale.com \
--to=german.rivera@freescale.com \
--cc=Geoff.Thorpe@freescale.com \
--cc=Kim.Phillips@freescale.com \
--cc=R89243@freescale.com \
--cc=agraf@suse.de \
--cc=arnd@arndb.de \
--cc=bhamciu1@freescale.com \
--cc=bhupesh.sharma@freescale.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nir.erez@freescale.com \
--cc=richard.schmitt@freescale.com \
--cc=scottwood@freescale.com \
--cc=stuart.yoder@freescale.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