From: Darren Hart <dvhart@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: linux-next: New platform-drivers-x86 tree
Date: Tue, 2 Sep 2014 22:21:20 -0700 [thread overview]
Message-ID: <20140903052120.GA39165@vmdeb7> (raw)
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.
I picked up maintenance of platform-drivers-x86 from Matthew Garrett. I wanted
to point you at my latest tree and make sure I understood the process for
working with linux-next.
The new tree is here:
git://git.infradead.org/users/dvhart/linux-platform-drivers-x86.git
I'm planning on pushing patches I'm considering for pull requests to the
'for-next' branch - unless you direct me otherwise. This is typically after they
pass LKP testing in the 'testing' branch.
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?
Regards,
--
Darren Hart
Intel Open Source Technology Center
next reply other threads:[~2014-09-03 5:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 5:21 Darren Hart [this message]
2014-09-03 19:18 ` linux-next: New platform-drivers-x86 tree Mark Brown
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=20140903052120.GA39165@vmdeb7 \
--to=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;
as well as URLs for NNTP newsgroup(s).