From: Samuel Ortiz <sameo@linux.intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>,
NeilBrown <neilb@suse.de>
Cc: Liam Girdwood <lrg@ti.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] twl-regulator: define all feature flags in one place.
Date: Wed, 9 May 2012 21:50:41 +0200 [thread overview]
Message-ID: <20120509195041.GR1794@sortiz-mobl> (raw)
In-Reply-To: <20120502090848.GF4075@opensource.wolfsonmicro.com>
Hi Neil,
On Wed, May 02, 2012 at 10:08:49AM +0100, Mark Brown wrote:
> On Wed, May 02, 2012 at 06:44:50AM +1000, NeilBrown wrote:
> > twl-regulator has a collection of feature flags, some defined
> > in twl-core.c and one defined in i2c/twl.h.
> > This is confusing for anyone adding a new feature flag.
> >
> > So collect them together and place them in twl.h immediately
> > after the structure in which they are initially set.
>
> Please remember to always CC maintainers on patches and always use
> subject lines appropriate for the subsystem. Adding Samuel since this
> is not a regulator patch.
Could you please re-send this patch to me ?
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2012-05-09 19:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 20:44 [PATCH 0/2] Make TWL4030_ALLOW_UNSUPPORTED more configurable NeilBrown
2012-05-01 20:44 ` [PATCH 1/2] twl-regulator: define all feature flags in one place NeilBrown
2012-05-02 9:08 ` Mark Brown
2012-05-09 19:50 ` Samuel Ortiz [this message]
2012-05-09 20:29 ` Mark Brown
2012-05-01 20:44 ` [PATCH 2/2] twl-regulator: make TWL4030_ALLOW_UNSUPPORTED more configurable NeilBrown
2012-05-02 9:11 ` Mark Brown
2012-05-08 18:40 ` Mark Brown
2012-05-08 19:47 ` NeilBrown
2012-05-09 9:03 ` Mark Brown
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=20120509195041.GR1794@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=neilb@suse.de \
/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.