From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"khilman@baylibre.com" <khilman@baylibre.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Subject: Re: [PATCH] ARC: Remove CONFIG_INITRAMFS_SOURCE from defconfigs
Date: Fri, 6 Jul 2018 13:06:51 +0000 [thread overview]
Message-ID: <ebb7bf8e51d6d50ef950ad6c16bbf879b6f7ee75.camel@synopsys.com> (raw)
In-Reply-To: <CAOi56cVxHKh4V1i8W8wS+n3E88UbzBiCo0PozhCeoN3YEnVmBw@mail.gmail.com>
Hi Vineet,
On Wed, 2018-06-06 at 09:32 -0700, Kevin Hilman wrote:
> On Wed, Jun 6, 2018 at 5:59 AM, Alexey Brodkin
> <Alexey.Brodkin@synopsys.com> wrote:
> > We used to have pre-set CONFIG_INITRAMFS_SOURCE with local path
> > to intramfs in ARC defconfigs. This was quite convenient for
> > in-house development but not that convenient for newcomers
> > who obviusly don't have folders like "arc_initramfs" next to
> > the Linux source tree. Which leads to quite surprising failure
> > of defconfig building:
> > ------------------------------->8-----------------------------
> > ../scripts/gen_initramfs_list.sh: Cannot open '../../arc_initramfs_hs/'
> > ../usr/Makefile:57: recipe for target 'usr/initramfs_data.cpio.gz' failed
> > make[2]: *** [usr/initramfs_data.cpio.gz] Error 1
> > ------------------------------->8-----------------------------
> >
> > So now when more and more people start to deal with our defconfigs
> > let's make their life easier with removal of CONFIG_INITRAMFS_SOURCE.
> >
> > Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> > Cc: Kevin Hilman <khilman@baylibre.com>
> > Cc: stable@vger.kernel.org
> >
> > Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
>
> Reviewed-by: Kevin Hilman <khilman@baylibre.com>
> Tested-by: Kevin Hilman <khilman@baylibre.com>
Any chance for this one to hit upstream sometime soon?
-Alexey
prev parent reply other threads:[~2018-07-06 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 12:59 Alexey Brodkin
2018-06-06 16:32 ` Kevin Hilman
2018-07-06 13:06 ` Alexey Brodkin [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=ebb7bf8e51d6d50ef950ad6c16bbf879b6f7ee75.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@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
all inboxes | Powered by JetHome®