public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Kars de Jong <jongk@linux-m68k.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux/m68k kernel mailing list <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH] MVME16x: add support for EARLY_PRINTK
Date: Tue, 25 Nov 2008 10:58:41 +0100	[thread overview]
Message-ID: <1227607121.9242.5.camel@kars.perseus.home> (raw)
In-Reply-To: <200811250226.54137.zippel@linux-m68k.org>

On di, 2008-11-25 at 02:26 +0100, Roman Zippel wrote:
> On Thursday 20. November 2008, Kars de Jong wrote:
> > diff --git a/arch/m68k/Kconfig.debug b/arch/m68k/Kconfig.debug
> > index f53b6d5..e0283a0 100644
> > --- a/arch/m68k/Kconfig.debug
> > +++ b/arch/m68k/Kconfig.debug
> > @@ -2,4 +2,15 @@ menu "Kernel hacking"
> >
> >  source "lib/Kconfig.debug"
> >
> > +config EARLY_PRINTK
> > +	bool "Early printk" if EMBEDDED
> > +	depends on MVME16x
> > +	default y
> > +	help
> 
> This is really misnamed, the option is mvme specific but the name is rather 
> generic. Depending on the code size you could include the code 
> unconditionally (like we do on other ports).

Defining CONFIG_EARLY_PRINTK used to pull in some generic code, that's
why I named it like that.

I grepped the source for CONFIG_EARLY_PRINTK, it seems the generic code
is gone.

So I think I'll just define it unconditionally, and only on MVME16x it
will actually include some extra code. Is that OK with you?


Kind regards, Kars.



  reply	other threads:[~2008-11-25  9:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-20 13:08 [PATCH] MVME16x: add support for EARLY_PRINTK Kars de Jong
2008-11-21 10:29 ` Geert Uytterhoeven
2008-11-21 12:27   ` Kars de Jong
2008-11-25  1:26 ` Roman Zippel
2008-11-25  9:58   ` Kars de Jong [this message]
2008-11-25 16:59     ` Roman Zippel

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=1227607121.9242.5.camel@kars.perseus.home \
    --to=jongk@linux-m68k.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=zippel@linux-m68k.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