From: Sekhar Nori <nsekhar@ti.com>
To: ARM-SoC Maintainers <soc@kernel.org>
Cc: Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] DaVinci SoC updates for v5.10
Date: Tue, 6 Oct 2020 09:55:03 +0530 [thread overview]
Message-ID: <0666c082-fa97-0231-cb42-83c995112b30@ti.com> (raw)
In-Reply-To: <83eff002-5247-4fb6-33b4-ce7cec3d2d5c@ti.com>
Hi ARM SoC team,
On 29/09/20 12:33 AM, Sekhar Nori wrote:
> The following changes since commit 9123e3a74ec7b934a4a099e98af6a61c2f80bbf5:
>
> Linux 5.9-rc1 (2020-08-16 13:04:57 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/nsekhar/linux-davinci.git tags/davinci-for-v5.10/soc
Can you please pull this?
Thanks,
Sekhar
>
> for you to fetch changes up to 7de3f326dd24b5e2d514f9cf99968a20d13cf39f:
>
> ARM: davinci: use simple i2c probe function (2020-09-03 11:09:19 +0530)
>
> ----------------------------------------------------------------
> This pull request contains a patch that shifts to using new simplified
> i2c driver probe method inside mach-davinci (i2c_driver->probe_new())
>
> ----------------------------------------------------------------
> Stephen Kitt (1):
> ARM: davinci: use simple i2c probe function
>
> arch/arm/mach-davinci/board-dm644x-evm.c | 5 ++---
> arch/arm/mach-davinci/board-dm646x-evm.c | 10 ++++------
> 2 files changed, 6 insertions(+), 9 deletions(-)
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
_______________________________________________
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-10-06 4:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 19:03 [GIT PULL] DaVinci SoC updates for v5.10 Sekhar Nori
2020-10-06 4:25 ` Sekhar Nori [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=0666c082-fa97-0231-cb42-83c995112b30@ti.com \
--to=nsekhar@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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).