All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Grant Likely <grant.likely@secretlab.ca>,
	Michael Trimarchi <michael@amarulasolutions.com>,
	linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH v3] gpio: twl4030: Cache the direction and output states in private data
Date: Thu, 17 Jan 2013 14:45:07 +0100	[thread overview]
Message-ID: <50F80063.5080803@ti.com> (raw)
In-Reply-To: <CACRpkdaj5mKk3hy9_QmjcDw3KhZt1Zdx1CXB6ZWmvbhhRWyndA@mail.gmail.com>

Hi Linus,

On 01/17/2013 11:43 AM, Linus Walleij wrote:
> On Thu, Jan 10, 2013 at 2:09 PM, Peter Ujfalusi <peter.ujfalusi@ti.com> wrote:
>> On 01/10/2013 11:41 AM, Linus Walleij wrote:
> 
>>> Sorry Peter this must have been missed somehow.
>>>
>>> This does not apply to the current v3.8-rc3, could you respin
>>> this on top of Torvalds' tree?
>>
>> Grant applied the patch which this one depends on:
>> [1] https://patchwork.kernel.org/patch/1844511/
> 
> Hm, it is not in mainline, nor on Grant's "merge" or "next"
> branches so it must have fallen on the floor somehow.
> 
> I applied both the patches not, thanks!

Thank you, I was planning to go through my pending patches tomorrow and resend
or annoy maintainers with them.

Thanks again,
Péter

WARNING: multiple messages have this Message-ID (diff)
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Grant Likely <grant.likely@secretlab.ca>,
	Michael Trimarchi <michael@amarulasolutions.com>,
	<linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v3] gpio: twl4030: Cache the direction and output states in private data
Date: Thu, 17 Jan 2013 14:45:07 +0100	[thread overview]
Message-ID: <50F80063.5080803@ti.com> (raw)
In-Reply-To: <CACRpkdaj5mKk3hy9_QmjcDw3KhZt1Zdx1CXB6ZWmvbhhRWyndA@mail.gmail.com>

Hi Linus,

On 01/17/2013 11:43 AM, Linus Walleij wrote:
> On Thu, Jan 10, 2013 at 2:09 PM, Peter Ujfalusi <peter.ujfalusi@ti.com> wrote:
>> On 01/10/2013 11:41 AM, Linus Walleij wrote:
> 
>>> Sorry Peter this must have been missed somehow.
>>>
>>> This does not apply to the current v3.8-rc3, could you respin
>>> this on top of Torvalds' tree?
>>
>> Grant applied the patch which this one depends on:
>> [1] https://patchwork.kernel.org/patch/1844511/
> 
> Hm, it is not in mainline, nor on Grant's "merge" or "next"
> branches so it must have fallen on the floor somehow.
> 
> I applied both the patches not, thanks!

Thank you, I was planning to go through my pending patches tomorrow and resend
or annoy maintainers with them.

Thanks again,
Péter

  reply	other threads:[~2013-01-17 13:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-20  9:44 [PATCH v3] gpio: twl4030: Cache the direction and output states in private data Peter Ujfalusi
2012-12-20  9:44 ` Peter Ujfalusi
2013-01-10 10:41 ` Linus Walleij
2013-01-10 13:09   ` Peter Ujfalusi
2013-01-10 13:09     ` Peter Ujfalusi
2013-01-17 10:43     ` Linus Walleij
2013-01-17 13:45       ` Peter Ujfalusi [this message]
2013-01-17 13:45         ` Peter Ujfalusi
2013-02-09 14:15     ` Grant Likely

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=50F80063.5080803@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=michael@amarulasolutions.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.