From: Olof Johansson <olof@lixom.net>
To: Sekhar Nori <nsekhar@ti.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
ARM-SoC Maintainers <soc@kernel.org>,
ARM-SoC Maintainers <arm@kernel.org>,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] DaVinci SoC updates for v5.6
Date: Mon, 27 Jan 2020 07:31:20 -0800 [thread overview]
Message-ID: <CAOesGMh4w0w5Q-VTtHxSBU5rRUtaN--4oB3xfXPTk_Z+Aeru0Q@mail.gmail.com> (raw)
In-Reply-To: <0b4efa9c-b811-1083-ce9c-8a92903e3680@ti.com>
On Mon, Jan 27, 2020 at 12:54 AM Sekhar Nori <nsekhar@ti.com> wrote:
>
> Hi Arnd, Olof,
>
> On 14/01/20 11:48 PM, Sekhar Nori wrote:
> > The following changes since commit e42617b825f8073569da76dc4510bfa019b1c35a:
> >
> > Linux 5.5-rc1 (2019-12-08 14:57:55 -0800)
> >
> > are available in the Git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/nsekhar/linux-davinci.git tags/davinci-for-v5.6/soc
> >
> > for you to fetch changes up to 5e06d19694a463a012c2589e29078196eb209448:
> >
> > ARM: davinci: dm644x-evm: Add Fixed regulators needed for tlv320aic33 (2020-01-13 17:36:26 +0530)
>
> Can you please pull in this for v5.6? I have not seen it in linux-next
> still.
Odd, it does not seem to have been picked up by patchwork, so I missed
tracking it.
Merging it now into arm/late.
-Olof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-01-27 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 18:18 [GIT PULL] DaVinci SoC updates for v5.6 Sekhar Nori
2020-01-27 8:54 ` Sekhar Nori
2020-01-27 15:31 ` Olof Johansson [this message]
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=CAOesGMh4w0w5Q-VTtHxSBU5rRUtaN--4oB3xfXPTk_Z+Aeru0Q@mail.gmail.com \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=bgolaszewski@baylibre.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=soc@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).