linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Saravana Kannan <saravanak@google.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Frank Rowand <frowand.list@gmail.com>,
	linux-tegra <linux-tegra@vger.kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Jon Hunter <jonathanh@nvidia.com>, Marc Zyngier <maz@kernel.org>,
	Kevin Hilman <khilman@baylibre.com>,
	kernel-team@android.com
Subject: Re: [PATCH v2 0/2] of: property: Add fw_devlink support for more props
Date: Tue, 26 Jan 2021 09:22:53 +0100	[thread overview]
Message-ID: <YA/RXVNiO8Hj3d5c@kroah.com> (raw)
In-Reply-To: <20210121225712.1118239-1-saravanak@google.com>

On Thu, Jan 21, 2021 at 02:57:10PM -0800, Saravana Kannan wrote:
> Sending again because I messed up the To/Cc for the coverletter.
> 
> This series combines two patches [1] [2] that'd conflict.
> 
> Greg,
> 
> Can you please pull this into driver-core-next?

Now queued up, thanks.

greg k-h

  parent reply	other threads:[~2021-01-26 17:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 22:57 [PATCH v2 0/2] of: property: Add fw_devlink support for more props Saravana Kannan
2021-01-21 22:57 ` [PATCH v2 1/2] of: property: Add fw_devlink support for "gpio" and "gpios" binding Saravana Kannan
2021-01-22 12:58   ` Linus Walleij
2021-01-21 22:57 ` [PATCH v2 2/2] of: property: Add fw_devlink support for interrupts Saravana Kannan
     [not found]   ` <CGME20210204115252eucas1p2d145686f7a5dc7e7a04dddd0b0f2286c@eucas1p2.samsung.com>
2021-02-04 11:52     ` Marek Szyprowski
2021-02-04 21:31       ` Saravana Kannan
2021-02-05  7:38         ` Marek Szyprowski
2021-02-05  8:06           ` Geert Uytterhoeven
2021-02-05 10:05             ` Saravana Kannan
2021-02-05 10:20               ` Geert Uytterhoeven
2021-02-05 17:19                 ` Saravana Kannan
2021-02-05 17:51                   ` Geert Uytterhoeven
2021-02-05 17:55                     ` Saravana Kannan
2021-02-06  4:32                       ` Saravana Kannan
2021-02-08  8:14                         ` Marek Szyprowski
2021-02-08 23:57                           ` Saravana Kannan
2021-02-13 18:54   ` Guenter Roeck
2021-02-14 21:12     ` Saravana Kannan
2021-02-15  3:06       ` Guenter Roeck
2021-02-15  3:58       ` Guenter Roeck
2021-02-15  8:29         ` Saravana Kannan
2021-02-15  9:08           ` Marc Zyngier
2021-02-15 22:23             ` Saravana Kannan
2021-01-26  8:22 ` Greg Kroah-Hartman [this message]
     [not found] ` <20210131163823.c4zb47pl4tukcl7c@viti.kaiser.cx>
2021-01-31 21:05   ` [PATCH v2 0/2] of: property: Add fw_devlink support for more props Saravana Kannan
2021-02-01 10:52     ` Martin Kaiser
2021-02-01 20:04       ` Saravana Kannan

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=YA/RXVNiO8Hj3d5c@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bgolaszewski@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=jonathanh@nvidia.com \
    --cc=kernel-team@android.com \
    --cc=khilman@baylibre.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=saravanak@google.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 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).