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] [day] [month] [year] [list]
Message-ID: <20150317075314.GA28026@kroah.com>
Date:	Tue, 17 Mar 2015 08:53:14 +0100
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Alexander Graf <agraf@...e.de>
Cc:	"J. German Rivera" <German.Rivera@...escale.com>, arnd@...db.de,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
	stuart.yoder@...escale.com, Kim.Phillips@...escale.com,
	scottwood@...escale.com, bhamciu1@...escale.com,
	R89243@...escale.com, bhupesh.sharma@...escale.com,
	nir.erez@...escale.com, richard.schmitt@...escale.com
Subject: Re: [PATCH] staging: fsl-mc: Corrected email addresses in TODO file

On Tue, Mar 17, 2015 at 08:14:42AM +0100, Alexander Graf wrote:
> 
> 
> On 12.03.15 04:52, J. German Rivera wrote:
> > Signed-off-by: J. German Rivera <German.Rivera@...escale.com>
> 
> Greg, going forward, how would you prefer to get patches for fsl-mc?
> There are a few options that I can see:
> 
>   1) individual patches on the ML for review, directly applied by you
>   2) individual patches on the ML for review, regular big patch sets
> from German to you
>   3) individual patches on the ML for review, regular pull requests from
> German to you
> 
> 
> I would personally prefer either 2 or 3, as that allows German to be the
> gatekeeper and grow responsibility for the upstream tree.

2 is fine, but note that I will pick up "cleanup" patches automatically,
no need for anyone else to be involved, as that's part of being in
staging.

thanks,

greg k-h
--
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