linux-kernel - Re: [PATCH] staging: fsl-mc: Corrected email addresses in TODO file

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]

Message-ID: <5507D462.4020504@suse.de>
Date:	Tue, 17 Mar 2015 08:14:42 +0100
From:	Alexander Graf <agraf@...e.de>
To:	"J. German Rivera" <German.Rivera@...escale.com>,
	gregkh@...uxfoundation.org, arnd@...db.de,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
CC:	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 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.

Alex
--
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/