From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Rob Herring <robherring2@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Frank Rowand <frowand.list@gmail.com>,
devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Devicetree fixes for 5.3-rc, take 2
Date: Sat, 27 Jul 2019 13:06:53 +0200 [thread overview]
Message-ID: <20190727110653.GF458@kroah.com> (raw)
In-Reply-To: <CAL_JsqJLB4q6wqTOX0oXAGQF4wuZ0irNT8nmpFEmuUKjvv38BQ@mail.gmail.com>
On Fri, Jul 26, 2019 at 06:03:50PM -0600, Rob Herring wrote:
> Hi Linus,
>
> Please pull some more DT fixes for 5.3. The nvmem changes would
> typically go thru Greg's tree, but they were missed in the merge
> window and I've been unable to get a response (partly because Srinivas
> is out on vacation it appears).
No objection from me for this.
thanks,
greg k-h
next prev parent reply other threads:[~2019-07-27 11:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-27 0:03 [GIT PULL] Devicetree fixes for 5.3-rc, take 2 Rob Herring
2019-07-27 11:06 ` Greg Kroah-Hartman [this message]
2019-07-27 16:35 ` pr-tracker-bot
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=20190727110653.GF458@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robherring2@gmail.com \
--cc=torvalds@linux-foundation.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).