lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 19 Oct 2009 17:24:44 +0200
From:	Peter Hüwe <PeterHuewe@....de>
To:	"Greg Kroah-Hartman" <gregkh@...e.de>
Cc:	Jiri Kosina <jkosina@...e.cz>, Alan Cox <alan@...ux.intel.com>,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
	kernel-janitors@...r.kernel.org
Subject: Re: [PATCH] staging/et131x:  adding __init/__exit macros

Am Tuesday 29 September 2009 11:10:01 schrieb Jiri Kosina:
> On Tue, 29 Sep 2009, Peter Huewe wrote:
> > From: Peter Huewe <peterhuewe@....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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ