public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH] m68k: generalize uboot command line support
Date: Fri, 9 Sep 2016 22:27:32 +1000	[thread overview]
Message-ID: <2e692fe4-67b8-36d5-262b-cedff400f262@linux-m68k.org> (raw)
In-Reply-To: <CAMuHMdUKLufiHyRuo3HhrXZ-fcDK5=qQ3mMsguKk2xBXtbrnjQ@mail.gmail.com>

Hi Geert,

On 09/09/16 17:33, Geert Uytterhoeven wrote:
> Hi Greg,
>
> On Fri, Sep 9, 2016 at 9:13 AM, Greg Ungerer <gerg@linux-m68k.org> wrote:
>> The uboot command line support needs to be used by both MMU and no-MMU
>> setups, but currently we only have the code in the no-MMU code paths.
>> Move the uboot command line processing code into its own file. Add
>> appropriate calls to it from both the MMU and no-MMU arch setup code.
>>
>> Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
>
> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
>
> If you want me to take this through the m68k tree instead, just let me know.
> Thanks!

Thanks. I have a few things queued (with the ColdFire 54411 MMU
changes) so I don't mind taking this one too.

Regards
Greg

  reply	other threads:[~2016-09-09 12:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09  7:13 [PATCH] m68k: generalize uboot command line support Greg Ungerer
2016-09-09  7:33 ` Geert Uytterhoeven
2016-09-09 12:27   ` Greg Ungerer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-09-09  1:10 Greg Ungerer
2016-09-09  6:20 ` Geert Uytterhoeven
2016-09-09  6:48   ` Greg Ungerer

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=2e692fe4-67b8-36d5-262b-cedff400f262@linux-m68k.org \
    --to=gerg@linux-m68k.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.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