From: Arnd Bergmann <arnd@arndb.de>
To: Santosh Shilimkar <santosh.shilimkar@oracle.com>
Cc: arm-soc <arm@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Kevin Hilman <khilman@kernel.org>,
Olof Johansson <olof@lixom.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] soc: ti: couple of non critical fixes for v5.1
Date: Fri, 15 Feb 2019 18:02:24 +0100 [thread overview]
Message-ID: <CAK8P3a3pspTHpVNDxwLG-GyajyjLN4nRz4k-3uUqwOP3xJzP3w@mail.gmail.com> (raw)
In-Reply-To: <1549044263-5862-1-git-send-email-santosh.shilimkar@oracle.com>
On Fri, Feb 1, 2019 at 7:04 PM Santosh Shilimkar
<santosh.shilimkar@oracle.com> wrote:
> soc: ti: couple of non critical fixes for v5.1
>
> - Fix the Clang warning for enum in Navigator dma
> - Simplify code in ti_sci with DEFINE_SHOW_ATTRIBUTE macro
Pulled into arm/drivers, thanks!
Arnd
prev parent reply other threads:[~2019-02-15 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 18:04 [GIT PULL] soc: ti: couple of non critical fixes for v5.1 Santosh Shilimkar
2019-02-15 17:02 ` Arnd Bergmann [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=CAK8P3a3pspTHpVNDxwLG-GyajyjLN4nRz4k-3uUqwOP3xJzP3w@mail.gmail.com \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=santosh.shilimkar@oracle.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).