linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sekhar Nori <nsekhar@ti.com>
To: Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Kevin Hilman <khilman@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	stable <stable@vger.kernel.org>, "Andrew F . Davis" <afd@ti.com>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/5] ARM: davinci: da830-evm: fix label names in GPIO lookup entries
Date: Fri, 11 Jan 2019 16:26:06 +0530	[thread overview]
Message-ID: <7d73f52d-e6e3-296c-ea87-6a0cf43afb0f@ti.com> (raw)
In-Reply-To: <CACRpkdapcG1bWCOk=SWHfKvpPMdBiEu0QOj4M+Zbx11Xhc59cA@mail.gmail.com>

Hi Linus,

On 11/01/19 3:08 PM, Linus Walleij wrote:
> On Thu, Jan 3, 2019 at 4:11 PM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> 
>> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>>
>> Since commit 587f7a694f01 ("gpio: davinci: Use dev name for label and
>> automatic base selection") the gpiochip label no longer has an ID
>> suffix. Update the GPIO lookup entries.
>>
>> Fixes: 587f7a694f01 ("gpio: davinci: Use dev name for label and automatic base selection")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> 
> The series:
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> 
> I suppose you will push this upstream through ARM SoC.

I sent a pull request with these applied to ARM SoC yesterday.

Thanks,
Sekhar

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-01-11 10:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-03 15:10 [PATCH 0/5] ARM: davinci: fix label names in GPIO lookup entries Bartosz Golaszewski
2019-01-03 15:11 ` [PATCH 1/5] ARM: davinci: da830-evm: " Bartosz Golaszewski
2019-01-11  9:38   ` Linus Walleij
2019-01-11 10:56     ` Sekhar Nori [this message]
2019-01-03 15:11 ` [PATCH 2/5] ARM: davinci: da850-evm: " Bartosz Golaszewski
2019-01-03 15:11 ` [PATCH 3/5] ARM: davinci: dm355-evm: " Bartosz Golaszewski
2019-01-03 15:11 ` [PATCH 4/5] ARM: davinci: dm644x-evm: " Bartosz Golaszewski
2019-01-03 15:11 ` [PATCH 5/5] ARM: davinci: omapl138-hawk: " Bartosz Golaszewski
2019-01-04  8:15 ` [PATCH 0/5] ARM: davinci: " Sekhar Nori

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=7d73f52d-e6e3-296c-ea87-6a0cf43afb0f@ti.com \
    --to=nsekhar@ti.com \
    --cc=afd@ti.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=brgl@bgdev.pl \
    --cc=khilman@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).