From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759164AbcIPKSa (ORCPT ); Fri, 16 Sep 2016 06:18:30 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:58642 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757082AbcIPKSW (ORCPT ); Fri, 16 Sep 2016 06:18:22 -0400 Date: Fri, 16 Sep 2016 11:18:07 +0100 From: Mark Brown To: Greg KH Cc: Arnd Bergmann , linux-kernel@vger.kernel.org, Johan Hovold , Rui Miguel Silva , Laurent Pinchart , Sandeep Patil , Matt Porter , John Stultz , Rob Herring , Viresh Kumar , Alex Elder , David Lin , "Bryan O'Donoghue" , Vaibhav Agarwal , Mark Greer Message-ID: <20160916101807.GV27974@sirena.org.uk> References: <20160914100949.GA6179@kroah.com> <20160915144553.GA15697@sirena.org.uk> <20160916060519.GA17586@kroah.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="rNtUoUA3Tn0/N1iC" Content-Disposition: inline In-Reply-To: <20160916060519.GA17586@kroah.com> X-Cookie: Even bytes get lonely for a little bit. User-Agent: Mutt/1.6.0 (2016-04-01) X-SA-Exim-Connect-IP: 2a01:348:6:8808:fab::3 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [GIT PULL] Greybus driver subsystem for 4.9-rc1 X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: No (on mezzanine.sirena.org.uk); Unknown failure Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --rNtUoUA3Tn0/N1iC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Sep 16, 2016 at 08:05:19AM +0200, Greg KH wrote: > On Thu, Sep 15, 2016 at 03:45:53PM +0100, Mark Brown wrote: > > Sending a pull request for code that's never been seen upstream seems > > completely premature. > Hey, how does code get upstream then? :) By having the actual code to the mailing list. > As for the drivers all living under drivers/greybus/ I understand, but > we need the greybus core present first before we can get the drivers in. > How about we do what happened with IIO, we take the greybus core code in > drivers/greybus/ and put the drivers in staging, and then move them out > of staging into the "real" portion of the kernel as they get reviewed > and accepted? Yes, staging would be appropriate for unreviewed code. --rNtUoUA3Tn0/N1iC Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJX28beAAoJECTWi3JdVIfQ+kwH/0FoDpoQCpzPL6AHAtrP8sJP fY7EKlxMQaHYBvtvkRkqPVrePKZviVKUYpPlofvtxP+1YwdUDD77pIcr3MBl3kTp LglvvMpUBX2Kx5Q7aGF4TSsPkbNNww3ky7DSlt7k9gvJ2qqGvkIIqd/He377zc9U dgLR/ie0oyzAPs4qfcyfCDUa1qd8Q5d1akUvbKTNcwu7Lgftb+35l62SqVyMALg8 Dbd797I3ryIRKNKrCYS+V+wu4rV4eWXFWWET0S/79DCZeM04k7OqzLga/Fjthq2V JDZVZpKPMR+sB9WvmzsJu4A8bPHtqOkPYNADB9J1UkvAnUwBocjfdPKeeeQMeWg= =eDrr -----END PGP SIGNATURE----- --rNtUoUA3Tn0/N1iC--