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 16:48:16 +1000 [thread overview]
Message-ID: <39f9e22c-31f2-0be5-7a1e-6df33f79831b@linux-m68k.org> (raw)
In-Reply-To: <CAMuHMdVTKUNy49py59+PTAT+DBhgewj1cShW7qT=1zjXnzpD9Q@mail.gmail.com>
Hi Geert,
On 09/09/16 16:20, Geert Uytterhoeven wrote:
> Hi Greg,
>
> On Fri, Sep 9, 2016 at 3:10 AM, Greg Ungerer <gerg@linux-m68k.org> wrote:
>> --- a/arch/m68k/include/asm/bootinfo.h
>> +++ b/arch/m68k/include/asm/bootinfo.h
>> @@ -22,6 +22,10 @@ extern void save_bootinfo(const struct bi_record *bi);
>> static inline void save_bootinfo(const struct bi_record *bi) {}
>> #endif
>>
>> +#ifdef CONFIG_UBOOT
>> +void process_uboot_commandline(char *commandp, int size);
>> +#endif
>
> What about providing a dummy for the !CONFIG_UBOOT case..
>
>> --- a/arch/m68k/kernel/setup_mm.c
>> +++ b/arch/m68k/kernel/setup_mm.c
>> @@ -274,6 +274,9 @@ void __init setup_arch(char **cmdline_p)
>> strncpy(m68k_command_line, CONFIG_BOOTPARAM_STRING, CL_SIZE);
>> m68k_command_line[CL_SIZE - 1] = 0;
>> #endif /* CONFIG_BOOTPARAM */
>> +#if defined(CONFIG_UBOOT)
>> + process_uboot_commandline(&m68k_command_line[0], CL_SIZE);
>> +#endif
>
> ... so you can drop the #if and #endif here?
Yep, good idea. I'll re-spin with that.
Thanks
Greg
next prev parent reply other threads:[~2016-09-09 6:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 1:10 [PATCH] m68k: generalize uboot command line support Greg Ungerer
2016-09-09 6:20 ` Geert Uytterhoeven
2016-09-09 6:48 ` Greg Ungerer [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-09 7:13 Greg Ungerer
2016-09-09 7:33 ` Geert Uytterhoeven
2016-09-09 12:27 ` 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=39f9e22c-31f2-0be5-7a1e-6df33f79831b@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