From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 3/3] ARM: shmobile: Koelsch: enable Ether in defconfig
Date: Mon, 18 Nov 2013 07:04:22 +0000 [thread overview]
Message-ID: <20131118070422.GD27935@verge.net.au> (raw)
In-Reply-To: <52868C1B.2080505@cogentembedded.com>
On Sat, Nov 16, 2013 at 12:03:23AM +0300, Sergei Shtylyov wrote:
> Hello.
>
> On 11/15/2013 08:29 AM, Simon Horman wrote:
>
> >>Enable the Ether driver in 'koelsch_defconfig' along with DHCP autoconfiguration
> >>and NFS root.
>
> >>Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>
> >Thanks.
>
> >I think it is also appropriate to remove these too.
> >To be hones their inclusion appears to have been an error on my part.
> >And if nfsroot is being enabled it seems to be a good opportunity
> >to get rid of them.
>
> >CONFIG_BLK_DEV_INITRD=y
> >CONFIG_INITRAMFS_SOURCE="../../initramfs/out/rootfs.arm.cpio"
> >CONFIG_INITRAMFS_COMPRESSION_GZIP=y
>
> Hm, where are you seeing these? Tag renesas-devel-v3.12-20131112
> doesn't contain anything similar...
Sorry, please ignore the noise.
I must have been looking at a local version by mistake.
prev parent reply other threads:[~2013-11-18 7:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 22:17 [PATCH v2 0/3] Add Ether support for R8A7791/Koelsch board Sergei Shtylyov
2013-11-14 22:19 ` [PATCH v2 1/3] ARM: shmobile: r8a7791: add Ether clock Sergei Shtylyov
2013-11-14 22:21 ` [PATCH v2 2/3] ARM: shmobile: Koelsch: add Ether support Sergei Shtylyov
2013-11-14 23:06 ` Laurent Pinchart
2013-11-15 20:28 ` Sergei Shtylyov
2013-11-15 23:03 ` Laurent Pinchart
2013-11-16 0:32 ` Sergei Shtylyov
2013-11-16 14:11 ` Laurent Pinchart
2013-11-18 7:05 ` Simon Horman
2013-11-14 22:23 ` [PATCH v2 3/3] ARM: shmobile: Koelsch: enable Ether in defconfig Sergei Shtylyov
2013-11-15 5:29 ` Simon Horman
2013-11-15 20:03 ` Sergei Shtylyov
2013-11-18 7:04 ` Simon Horman [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=20131118070422.GD27935@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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).