From: Lee Jones <lee.jones@linaro.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: sameo@linux.intel.com, patches@opensource.wolfsonmicro.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: arizona: Update volatile registers for WM5110 DSP
Date: Tue, 17 Sep 2013 10:54:07 +0100 [thread overview]
Message-ID: <20130917095407.GV16984@lee--X1> (raw)
In-Reply-To: <20130917091823.GF3635@opensource.wolfsonmicro.com>
> No problem sorry the commit message was a little vague there.
> Seems I accidentally generated the first version of this patch
> against the ASoC tree, but this got me thinking now you are
> looking after MFD patches which tree should I be generating them
> against?
That depends. If you are submitting MFD only patches and you base them
on either Sam's [1] or my tree [2], you probably won't go too far
wrong.
However, if your patch or patch-set touches other subsystems then the
latest -rc is usually appropriate.
> On Tue, Sep 17, 2013 at 08:24:25AM +0100, Lee Jones wrote:
> > On Mon, 16 Sep 2013, Charles Keepax wrote:
> >
> > Any chance of a little more information in the commit message?
> >
> > What are scratch registers and why are they required now where they
> > weren't before? Why are the control and clocking regulators no longer
> > needed?
[1] git://git.kernel.org/pub/scm/linux/kernel/git/sameo/mfd-next.git - master
[2] git://git.linaro.org/people/ljones/mfd.git - for-mfd-next
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2013-09-17 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 15:31 [PATCH] mfd: arizona: Update volatile registers for WM5110 DSP Charles Keepax
2013-09-17 7:24 ` Lee Jones
2013-09-17 9:18 ` Charles Keepax
2013-09-17 9:54 ` Lee Jones [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=20130917095407.GV16984@lee--X1 \
--to=lee.jones@linaro.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sameo@linux.intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.