mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bryan Wu" <cooloney@kernel.org>
To: "Jörn Engel" <joern@logfs.org>
Cc: "Mike Frysinger" <vapier.adi@gmail.com>,
	linux-mtd@lists.infradead.org, dwmw2@infradead.org,
	will.newton@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] [MTD/MAPS] Blackfin Async Flash Maps: Handle the case where flash memory and ethernet mac/phy are mapped onto the same async bank
Date: Wed, 14 May 2008 10:50:31 +0800	[thread overview]
Message-ID: <386072610805131950l196c6bbera7242bf517a2b838@mail.gmail.com> (raw)
In-Reply-To: <20080513191616.GC18026@logfs.org>

On Wed, May 14, 2008 at 3:16 AM, Jörn Engel <joern@logfs.org> wrote:
>
> On Tue, 13 May 2008 13:42:04 -0400, Mike Frysinger wrote:
>  > On Tue, May 13, 2008 at 11:34 AM, Jörn Engel <joern@logfs.org> wrote:
>  > > On Tue, 13 May 2008 12:38:45 +0800, Bryan Wu wrote:
>  > > > +#define pr_devinit(fmt, args...) ({ static const __devinitdata char __fmt[] = fmt; printk(__fmt, ## args); })
>  > >
>  > >  That bit is obvious.  But why do you use pr_devinit() instead of
>  > >  printk()?  What does it gain you?
>  >
>  > why do we have __init and __devinit in the first place ?
>
>  Ah.  Now I finally understand what this code does.
>
>  Might be worth moving it to include/linux/kernel.h, along with
>  pr_init().  And watch an avalanche of janitor patches use these new
>  toys. :)
>

Yes, I agree. Mike, could you consider providing a patch to add
pr_devinit to common code?
IMO, your weapon can be shared by others.

Thanks
-Bryan

  reply	other threads:[~2008-05-14  2:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-13  4:38 Bryan Wu
2008-05-13  8:07 ` Jörn Engel
2008-05-13 12:42   ` Mike Frysinger
2008-05-13 15:01     ` Jörn Engel
2008-05-13 15:15       ` Mike Frysinger
2008-05-13 15:34         ` Jörn Engel
2008-05-13 17:42           ` Mike Frysinger
2008-05-13 19:16             ` Jörn Engel
2008-05-14  2:50               ` Bryan Wu [this message]
2008-05-13 17:41   ` Mike Frysinger

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=386072610805131950l196c6bbera7242bf517a2b838@mail.gmail.com \
    --to=cooloney@kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=joern@logfs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=vapier.adi@gmail.com \
    --cc=will.newton@gmail.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

all inboxes | Powered by JetHome®