public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: Greg Kroah-Hartman <gregkh@suse.de>
Cc: Jiri Kosina <jkosina@suse.cz>, Alan Cox <alan@linux.intel.com>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] staging/et131x:  adding __init/__exit macros
Date: Mon, 19 Oct 2009 15:24:44 +0000	[thread overview]
Message-ID: <200910191724.45300.PeterHuewe@gmx.de> (raw)
In-Reply-To: <alpine.LSU.2.00.0909291107410.9280@wotan.suse.de>

Am Tuesday 29 September 2009 11:10:01 schrieb Jiri Kosina:
> On Tue, 29 Sep 2009, Peter Huewe wrote:
> > From: Peter Huewe <peterhuewe@gmx.de>
> >
> > Trivial patch which adds the __init/__exit macros to the module_init/
> > module_exit functions of ./staging/et131x/et131x_initpci.c
> >
> > Greg, please have a look at the small patch and either pull it through
> > your staging tree, or please ack' it so Jiri can pull it through the
> > trivial tree.
>
> Greg -- I'd prefer you taking trivial staging fixes through yoru tree, as
> I expect we'll be conflicting soon due to the speed of changes in staging
> area, if you don't have any objections.
>
> Thanks,


Hi Greg,

any updates on this patch?
If I should recreate the patch against the linux-next tree, or your staging 
tree, please tell me.

Same applies to 
[PATCH] staging/cx25821:  adding __init/__exit macros
[PATCH] staging/p9auth:  adding __init/__exit macros
[PATCH] staging/phison:  adding __init/__exit macros
and somewhat also to
[PATCH] staging/panel: prevent driver from calling misc_deregister twice on 
same ressource


Thanks,
Peter



  parent reply	other threads:[~2009-10-19 15:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-28 23:34 [PATCH] staging/et131x: adding __init/__exit macros Peter Huewe
2009-09-29  9:10 ` Jiri Kosina
2009-09-29 15:30   ` Greg KH
2009-10-19 15:24   ` Peter Hüwe [this message]
2009-10-19 21:43     ` Greg KH
2009-10-19 22:04       ` Peter Huewe
2009-09-29 10:57 ` Alan Cox

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=200910191724.45300.PeterHuewe@gmx.de \
    --to=peterhuewe@gmx.de \
    --cc=alan@linux.intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=jkosina@suse.cz \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@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