From: Scott Wood <scottwood@freescale.com>
To: <Yuantian.Tang@freescale.com>
Cc: B07421@freescale.com, linuxppc-dev@lists.ozlabs.org,
Shaohui Xie <Shaohui.Xie@freescale.com>
Subject: Re: [PATCH] powerpc/config: add SCSI configs for corenet64_smp_defconfig
Date: Thu, 2 Apr 2015 18:56:22 -0500 [thread overview]
Message-ID: <1428018982.22867.310.camel@freescale.com> (raw)
In-Reply-To: <1427796008-40028-1-git-send-email-Yuantian.Tang@freescale.com>
On Tue, 2015-03-31 at 18:00 +0800, Yuantian.Tang@freescale.com wrote:
> From: Tang Yuantian <Yuantian.Tang@freescale.com>
>
> Otherwise there wil be no SCSI device nodes.
>
> Signed-off-by: Shaohui Xie <Shaohui.Xie@freescale.com>
> Signed-off-by: Tang Yuantian <Yuantian.Tang@freescale.com>
> ---
> arch/powerpc/configs/corenet64_smp_defconfig | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/arch/powerpc/configs/corenet64_smp_defconfig b/arch/powerpc/configs/corenet64_smp_defconfig
> index 04737aa..77a8151 100644
> --- a/arch/powerpc/configs/corenet64_smp_defconfig
> +++ b/arch/powerpc/configs/corenet64_smp_defconfig
> @@ -75,6 +75,13 @@ CONFIG_BLK_DEV_LOOP=y
> CONFIG_BLK_DEV_RAM=y
> CONFIG_BLK_DEV_RAM_SIZE=131072
> CONFIG_EEPROM_LEGACY=y
> +CONFIG_BLK_DEV_SD=y
> +CONFIG_CHR_DEV_ST=y
> +CONFIG_BLK_DEV_SR=y
> +CONFIG_CHR_DEV_SG=y
Ben already sent a patch enabling these (except ST -- do we really need
that?) in both corenet32 and corenet64.
> +CONFIG_SCSI_MULTI_LUN=y
This option was removed by c309b35171dd
> +CONFIG_SCSI_LOGGING=y
> +CONFIG_SCSI_SPI_ATTRS=y
If you want these enabled, do it in a separate patch with an explanation
of why we should enable them by default, and do it for other
85xx/corenet configs as well.
-Scott
next prev parent reply other threads:[~2015-04-02 23:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 10:00 [PATCH] powerpc/config: add SCSI configs for corenet64_smp_defconfig Yuantian.Tang
2015-04-02 23:56 ` Scott Wood [this message]
2015-04-03 2:08 ` Yuantian Tang
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=1428018982.22867.310.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=Shaohui.Xie@freescale.com \
--cc=Yuantian.Tang@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).