All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
	Peter Meerwald <pmeerw@pmeerw.net>,
	linux-iio@vger.kernel.org
Subject: Re: [PATCH 1/2] staging:iio:ad7606: Consolidate PM ops
Date: Sat, 6 Feb 2016 17:54:09 +0000	[thread overview]
Message-ID: <56B63341.10300@kernel.org> (raw)
In-Reply-To: <56B5D8E6.9060409@metafoo.de>

On 06/02/16 11:28, Lars-Peter Clausen wrote:
> On 02/06/2016 12:22 PM, Jonathan Cameron wrote:
>> On 05/02/16 10:32, Lars-Peter Clausen wrote:
>>> Both the SPI and platform device driver for the ad7606 use the same set of
>>> PM ops. Consolidate them in the common part of the driver.
>>>
>>> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
>> Lars, this doesn't apply to the togreg branch.
>>
>> Looks like you are locally missing the patch:
>>
>> 0046a46a8f93f5b99b499118779521ba3b017d69
>> staging/ad7606: Actually build the interface modules 
> 
> Which is not yet in the public togreg branch. I'll rebase and resend next
> week when the public branch has been updated.
Odd... Pull request went out last weekend and hence even if I'd accidentally
kept it in testing until then it should have been in togreg last week.
Ah well, definitely is now as it's made it through to staging-next (and
Linux next). oops!

Jonathan


      reply	other threads:[~2016-02-06 17:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05 10:32 [PATCH 1/2] staging:iio:ad7606: Consolidate PM ops Lars-Peter Clausen
2016-02-05 10:32 ` [PATCH 2/2] staging:iio:ad7606: Consolidate channel specs Lars-Peter Clausen
2016-02-06 11:24   ` Jonathan Cameron
2016-02-06 11:22 ` [PATCH 1/2] staging:iio:ad7606: Consolidate PM ops Jonathan Cameron
2016-02-06 11:28   ` Lars-Peter Clausen
2016-02-06 17:54     ` Jonathan Cameron [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=56B63341.10300@kernel.org \
    --to=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /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.