linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Brodkin <alexey.brodkin@synopsys.com>
To: Corentin Labbe <clabbe@baylibre.com>
Cc: "khilman@baylibre.com" <khilman@baylibre.com>,
	"linux-snps-arc@lists.infradead.org" 
	<linux-snps-arc@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Vineet Gupta <vineet.gupta1@synopsys.com>
Subject: RE: [PATCH resend] arc: hsdk_defconfig: Enable CONFIG_BLK_DEV_RAM
Date: Mon, 25 Feb 2019 14:07:21 +0000	[thread overview]
Message-ID: <4881796E12491D4BB15146FE0209CE646820111F@de02wembxa.internal.synopsys.com> (raw)
In-Reply-To: <1551087938-28594-1-git-send-email-clabbe@baylibre.com>

Hi Corentin,

> -----Original Message-----
> From: linux-snps-arc <linux-snps-arc-bounces@lists.infradead.org> On Behalf Of Corentin Labbe
> Sent: Monday, February 25, 2019 12:46 PM
> To: vineet.gupta1@synopsys.com
> Cc: khilman@baylibre.com; linux-snps-arc@lists.infradead.org; linux-kernel@vger.kernel.org; Corentin
> Labbe <clabbe@baylibre.com>
> Subject: [PATCH resend] arc: hsdk_defconfig: Enable CONFIG_BLK_DEV_RAM
> 
> We have now a HSDK device in our kernelci lab, but kernel builded via
> the hsdk_defconfig lacks ramfs supports, so it cannot boot kernelci jobs
> yet.
> 
> So this patch enable CONFIG_BLK_DEV_RAM in hsdk_defconfig.
> 
> Signed-off-by: Corentin Labbe <clabbe@baylibre.com>

Acked-by: Alexey Brodkin <abrodkin@synopsys.com>

      reply	other threads:[~2019-02-25 14:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-25  9:45 [PATCH resend] arc: hsdk_defconfig: Enable CONFIG_BLK_DEV_RAM Corentin Labbe
2019-02-25 14:07 ` 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=4881796E12491D4BB15146FE0209CE646820111F@de02wembxa.internal.synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --cc=clabbe@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=vineet.gupta1@synopsys.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;
as well as URLs for NNTP newsgroup(s).