All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
	Keerthy <j-keerthy@ti.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v2 1/2] drivers: provide devm_platform_ioremap_resource()
Date: Thu, 21 Feb 2019 13:06:54 +0100	[thread overview]
Message-ID: <CACRpkdauvLkMs6HQiuuBy9ACVB+zmYY6W8FqmdUUQFrYZcHjaQ@mail.gmail.com> (raw)
In-Reply-To: <CAMRc=Md0sqouS+p2RvW+fwM41eN5=P9Nd7V=gYuqxunfa3j-nA@mail.gmail.com>

On Thu, Feb 21, 2019 at 10:53 AM Bartosz Golaszewski <brgl@bgdev.pl> wrote:

> > > Should this go through the driver-core tree?
> >
> > No need, put it through the tree for patch 2/2.
> >
> > thanks,
> >
> > greg k-h
>
> Linus,
>
> can you take the two patches for v5.1?

Yup both merged to the GPIO tree, thanks!

Yours,
Linus Walleij

  reply	other threads:[~2019-02-21 12:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20 11:12 [PATCH v2 0/2] drivers: new helper for ioremapping memory resources Bartosz Golaszewski
2019-02-20 11:12 ` [PATCH v2 1/2] drivers: provide devm_platform_ioremap_resource() Bartosz Golaszewski
2019-02-20 11:16   ` Greg Kroah-Hartman
2019-02-20 11:21     ` Bartosz Golaszewski
2019-02-20 12:15       ` Greg Kroah-Hartman
2019-02-21  9:53         ` Bartosz Golaszewski
2019-02-21 12:06           ` Linus Walleij [this message]
2019-02-20 11:12 ` [PATCH v2 2/2] gpio: davinci: use devm_platform_ioremap_resource() Bartosz Golaszewski
2019-02-20 12:04 ` [PATCH v2 0/2] drivers: new helper for ioremapping memory resources Andy Shevchenko

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=CACRpkdauvLkMs6HQiuuBy9ACVB+zmYY6W8FqmdUUQFrYZcHjaQ@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=brgl@bgdev.pl \
    --cc=gregkh@linuxfoundation.org \
    --cc=j-keerthy@ti.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@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.