From: Samuel Ortiz <sameo@linux.intel.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Michael Hennerich <hennerich@blackfin.uclinux.org>,
device-drivers-devel@blackfin.uclinux.org
Subject: Re: [PATCH RESEND 1/3] mfd: Fix checking bit_mask for adp5520_set_bits
Date: Mon, 19 Dec 2011 18:54:57 +0100 [thread overview]
Message-ID: <20111219175457.GV11800@sortiz-mobl> (raw)
In-Reply-To: <CAF+7xWmHa1ef2nd0g7Gf+rjsxUemapSLK_uwHxYnNws2dy9h_w@mail.gmail.com>
Hi Axel,
On Mon, Dec 19, 2011 at 08:25:27PM +0800, Axel Lin wrote:
> 2011/12/19 Axel Lin <axel.lin@gmail.com>:
> > Current code checks if all the bit_mask bits are all zero is wrong.
> > We need to write new value if old value is not equal to new value.
> >
> > Signed-off-by: Axel Lin <axel.lin@gmail.com>
> > Acked-by: Michael Hennerich <michael.hennerich@analog.com>
> > ---
> > Hi Samuel,
> > I found this serial of patches are not merged yet.
> > ( although you replied that you applied all 3 patches in the mail )
> > It was post on https://lkml.org/lkml/2011/10/30/137
> > So I resend it again.
> >
> Hi Samuel,
> I found these patches already in your for-linus branch.
> But it is strange that these patches are not exist in linux-next tree.
Strange as in I forgot to cherry pick them. It should be fixed now, sorry.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2011-12-19 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 11:55 [PATCH RESEND 1/3] mfd: Fix checking bit_mask for adp5520_set_bits Axel Lin
2011-12-19 11:57 ` [PATCH RESEND 2/3] mfd: da903x: Ensure setting bits if new value is different from the old value Axel Lin
2011-12-19 11:59 ` [PATCH RESEND 3/3] mfd: tps6586x: " Axel Lin
2011-12-19 12:25 ` [PATCH RESEND 1/3] mfd: Fix checking bit_mask for adp5520_set_bits Axel Lin
2011-12-19 17:54 ` Samuel Ortiz [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=20111219175457.GV11800@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=axel.lin@gmail.com \
--cc=device-drivers-devel@blackfin.uclinux.org \
--cc=hennerich@blackfin.uclinux.org \
--cc=linux-kernel@vger.kernel.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 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.