public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Huewe <PeterHuewe@gmx.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] mtd: adding __init/__exit macros to init/exitfunctions of mtd drivers
Date: Mon, 22 Jun 2009 22:00:51 +0000	[thread overview]
Message-ID: <200906230000.51917.PeterHuewe@gmx.de> (raw)
In-Reply-To: <200906110223.33397.PeterHuewe@gmx.de>

Am Freitag 12 Juni 2009 11:03:19 schrieb Jiri Kosina:
> [ CCing dmmw2 -- please either Ack the patch so that I can take it through
>   trivial tree, or take it through your tree. Thanks.
>
> On Thu, 11 Jun 2009, Peter Hüwe wrote:
> > From: Peter Huewe <peterhuewe@gmx.de>
> >
> > Trivial patch which adds the __init and __exit macros to the module_init
> > / module_exit functions to the following modules from drivers/mtd/
> > devices/m25p80.c
> >  devices/slram.c
> >  linux version 2.6.30
> >  ftl.c
> >  nand/cafe_nand.c
> >  nand/cmx270_nand.c
> >
> > Signed-off-by: Peter Huewe <peterhuewe@gmx.de>

Hi,
@ dwmw2: can you please have a look at the trivial patch and if there is no 
problem with it ack it so Jiri can take it through the trivial tree or even 
better you take it through one of yours?
Would be very kind of you.

Thanks,
Peter
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-06-22 22:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11  0:23 [PATCH] mtd: adding __init/__exit macros to init/exitfunctions of mtd drivers Peter Hüwe
2009-06-12  9:03 ` [PATCH] mtd: adding __init/__exit macros to init/exitfunctions Jiri Kosina
2009-06-22 22:00 ` Peter Huewe [this message]
2009-07-01  9:14 ` [PATCH] mtd: adding __init/__exit macros to init/exitfunctions of mtd drivers Peter Hüwe
2009-07-01  9:44 ` [PATCH] mtd: adding __init/__exit macros to init/exitfunctions Jiri Kosina

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=200906230000.51917.PeterHuewe@gmx.de \
    --to=peterhuewe@gmx.de \
    --cc=kernel-janitors@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