public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: Axel Lin <axel.lin@ingics.com>
Cc: Harald Welte <laforge@openmoko.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mfd: pcf50633: Init pcf->dev before using it
Date: Sun, 27 Jan 2013 01:32:29 +0100	[thread overview]
Message-ID: <20130127003229.GG1174@sortiz-mobl> (raw)
In-Reply-To: <CAFRkauDQD4bA2VwrWVfzBcwY-A7y4VzQam8tB4L5HGNOS48uGA@mail.gmail.com>

Hi Axel,

On Fri, Jan 25, 2013 at 11:08:00AM +0800, Axel Lin wrote:
> 2013/1/22 Samuel Ortiz <sameo@linux.intel.com>
> 
> > Hi Axel,
> >
> > On Tue, Dec 25, 2012 at 10:52:49AM +0800, Axel Lin wrote:
> > > Current code uses pcf->dev in the dev_err call before setting it to
> > > &client->dev. Fix it.
> > >
> > > Signed-off-by: Axel Lin <axel.lin@ingics.com>
> > > ---
> > >  drivers/mfd/pcf50633-core.c |    5 ++---
> > >  1 file changed, 2 insertions(+), 3 deletions(-)
> > Applied to my for-linus branch, thanks.
> >
> 
> Hi Samuel,
> Seems the patches queued in your for-linus branch does not (yet) appear in
> linux-next?
for-linus goes to Linus and then they show up in linux-next.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

      parent reply	other threads:[~2013-01-27  0:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-25  2:52 [PATCH] mfd: pcf50633: Init pcf->dev before using it Axel Lin
2013-01-22  3:31 ` Samuel Ortiz
     [not found]   ` <CAFRkauDQD4bA2VwrWVfzBcwY-A7y4VzQam8tB4L5HGNOS48uGA@mail.gmail.com>
2013-01-27  0:32     ` 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=20130127003229.GG1174@sortiz-mobl \
    --to=sameo@linux.intel.com \
    --cc=axel.lin@ingics.com \
    --cc=laforge@openmoko.org \
    --cc=lars@metafoo.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox