linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@sifive.com>
To: linux@roeck-us.net
Cc: aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux@roeck-us.net
Subject: Re: [PATCH] riscv: Drop setup_initrd
Date: Mon, 20 Aug 2018 15:33:29 -0700 (PDT)	[thread overview]
Message-ID: <mhng-fabb487c-62df-4a45-b629-5a8f59d9bbb8@palmer-si-x1c4> (raw)
In-Reply-To: <1533874300-17656-1-git-send-email-linux@roeck-us.net>

On Thu, 09 Aug 2018 21:11:40 PDT (-0700), linux@roeck-us.net wrote:
> setup_initrd() does not appear to serve a practical purpose other than
> preventing qemu boots with "-initrd" parameter, so let's drop it.
>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> ---
>  arch/riscv/kernel/setup.c | 39 ---------------------------------------
>  1 file changed, 39 deletions(-)

I missed this for the merge window but I think it's suitable for an RC so I'll 
target it for next week.  It's at kernel.org/palmer/linux.git/fix-initrd and 
I've added it to for-next.

Thanks!

  parent reply	other threads:[~2018-08-20 22:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-10  4:11 [PATCH] riscv: Drop setup_initrd Guenter Roeck
2018-08-10  8:38 ` Christoph Hellwig
2018-08-20 22:33 ` Palmer Dabbelt [this message]
2018-08-28 20:10 ` Palmer Dabbelt
2018-08-28 20:59   ` Guenter Roeck
2018-08-28 21:25   ` Guenter Roeck
2018-08-28 21:46     ` Andreas Schwab
2018-08-28 21:59       ` Guenter Roeck
2018-08-28 22:03         ` Palmer Dabbelt
2018-08-28 22:12           ` Guenter Roeck
2018-08-29  0:09             ` Palmer Dabbelt
2018-08-29  0:36               ` Guenter Roeck
2018-08-29  0:49                 ` Palmer Dabbelt

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=mhng-fabb487c-62df-4a45-b629-5a8f59d9bbb8@palmer-si-x1c4 \
    --to=palmer@sifive.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux@roeck-us.net \
    /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).