From: Mark Brown <broonie@kernel.org>
To: Darren Hart <dvhart@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Subject: Re: linux-next: New platform-drivers-x86 tree
Date: Wed, 3 Sep 2014 20:18:07 +0100 [thread overview]
Message-ID: <20140903191807.GE29327@sirena.org.uk> (raw)
In-Reply-To: <20140903052120.GA39165@vmdeb7>
[-- Attachment #1: Type: text/plain, Size: 916 bytes --]
On Tue, Sep 02, 2014 at 10:21:20PM -0700, Darren Hart wrote:
> Hi Stephen,
>
> I searched the documentation (development-process/*) but found the linux-next
> wiki to be down (for a while now it seems). Apologies if I'm missing something
> documented there.
This is pretty much the process. Stephen's on holiday this week, I've
updated the configuration for the trees I'm building this week but you
might want to check that this gets carried over when he's back on
Monday.
> I have subscribed to the linux-next mailing list. Is there more I need to be
> doing? Do I need to send you pull requests, or do you pull a list of branches
> automatically?
It's all done automatically - for-next will be fetched for each -next
build. Stephen's form letter for this can be found in the archives, the
main rule is that you should only be putting code there intended to go
in during the merge window.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-09-03 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 5:21 linux-next: New platform-drivers-x86 tree Darren Hart
2014-09-03 19:18 ` Mark Brown [this message]
2014-09-08 0:46 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140903191807.GE29327@sirena.org.uk \
--to=broonie@kernel.org \
--cc=dvhart@infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox