linux-kernel - Re: [PATCH 3/3] [ARM] msm: add minimal board file for HTC Dream device

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: <20090625204630.GH11875@n2100.arm.linux.org.uk>
Date:	Thu, 25 Jun 2009 21:46:30 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Brian Swetland <swetland@...gle.com>
Cc:	Pavel Machek <pavel@....cz>,
	linux-arm-kernel@...ts.arm.linux.org.uk,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] [ARM] msm: add minimal board file for HTC Dream
	device

On Thu, Jun 25, 2009 at 12:31:03PM -0700, Brian Swetland wrote:
> On Thu, Jun 25, 2009 at 6:55 AM, Russell King - ARM
> Linux<linux@....linux.org.uk> wrote:
> > On Wed, Jun 24, 2009 at 10:56:19PM +0200, Pavel Machek wrote:
> >> Are there any issues that prevent this from being merged? Russell, can
> >> you take those patches?
> >
> > I thought Alan's preference was for me to be out of the loop on machine
> > specific stuff, and for platform maintainers to push their stuff directly
> > into linux-next and to Linus.
> >
> > If people do want to push stuff via me, that's fine, but they're going to
> > have to explicitly ask for it.  If they don't, that's also fine.  (There
> > are those who clearly stated that they want my continued involvement and
> > review.)
> 
> I wasn't sure when/how the process would change here.  Could somebody
> point me at any up to date information on how/where to send stuff to
> linux-next?

Documentation/development-process/2.Process, last bits of section 2.4.

> I'm still interested in sending patches past lakml/lkml for review
> though -- I've received very useful feedback from previous patches
> this way in the past.  Presumably (for arch/arm/mach-msm/...) I could
> send patch series out for review, adjust them as necessary based on
> feedback, and assemble into a git branch suitable for linux-next?

Still happy to do that.

linux-next only takes git branches, and when you talk to sfr he'll tell
you about what he wants to see in that branch.
--
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/