From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: Newbies question: Which tree do I base my mc13783-regulator patches on?
Date: Thu, 10 Mar 2011 16:01:02 +0000 [thread overview]
Message-ID: <20110310160102.GE7411@sirena.org.uk> (raw)
In-Reply-To: <4D78F0D9.7070408@hale.at>
On Thu, Mar 10, 2011 at 04:40:09PM +0100, Helmut Raiger wrote:
> I'm currently implementing the suspend functions of this regulator.
> Could anyone give me a quick start on how to submit the patches correctly?
Use git://git.kernel.org/pub/scm/linux/kernel/git/lrg/voltage-2.6
In general you'll usually be OK basing your work off -next without
worrying too much about individual trees as that includes the latest
development code for most of the kernel. You can look up individual
trees in MAINTAINERS.
prev parent reply other threads:[~2011-03-10 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 15:40 Newbies question: Which tree do I base my mc13783-regulator patches on? Helmut Raiger
2011-03-10 16:01 ` Mark Brown [this message]
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=20110310160102.GE7411@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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