From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] soc: Keystone SOC Navigator drivers for 3.18
Date: Tue, 23 Sep 2014 21:43:17 -0700 [thread overview]
Message-ID: <20140924044317.GB24803@localhost> (raw)
In-Reply-To: <1409865234-9932-1-git-send-email-santosh.shilimkar@ti.com>
On Thu, Sep 04, 2014 at 05:13:54PM -0400, Santosh Shilimkar wrote:
> Hi Arm-soc folks,
>
> Please pull below Keystone SOC drivers. They have been on the list for review
> for last few merge windows. I got handful of comments on DTS bindings which
> has been already addressed. This should ungate me to get network support for
> Keystone which is missing in mainline.
>
> The following changes since commit 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9:
>
> Linux 3.17-rc1 (2014-08-16 10:40:26 -0600)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git tags/drivers-soc-ti
>
> for you to fetch changes up to e9e7494bdcc7926237823253707691d0f3787be2:
>
> MAINTAINERS: Add Keystone Multicore Navigator drivers entry (2014-09-04 16:40:16 -0400)
>
> ----------------------------------------------------------------
> Keystone SOC Navigator drivers for 3.18
>
> The Keystone Multi-core Navigator contains QMSS and packet DMA
> subsystems which interwork together to form the Navigator cloud
> used by various subsystems like NetCP, SRIO, SideBand Crypto
> engines etc.
>
> ----------------------------------------------------------------
> Sandeep Nair (3):
> firmware: add Keystone QMSS PDSP accumulator firmware blob
> Documentation: dt: soc: add Keystone Navigator QMSS bindings
> soc: ti: add Keystone Navigator QMSS driver
>
> Santosh Shilimkar (3):
> Documentation: dt: soc: add Keystone Navigator DMA bindings
> soc: ti: add Keystone Navigator DMA support
> MAINTAINERS: Add Keystone Multicore Navigator drivers entry
Hi Santosh,
I was going through the queue of merges to do and it seems like Arnd
missed this one.
Before I merge it though -- it looks like the firmware should be added to
the linux-firmware repository instead? We try to avoid adding new firmware
files in the kernel tree these days and get them from there instead...
Can you respin with that fixed, or should I cherry-pick the contents from
this branch instead (all but that patch)?
-Olof
next prev parent reply other threads:[~2014-09-24 4:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 21:13 [GIT PULL] soc: Keystone SOC Navigator drivers for 3.18 Santosh Shilimkar
2014-09-24 4:43 ` Olof Johansson [this message]
2014-09-24 13:57 ` Santosh Shilimkar
2014-09-24 17:36 ` Olof Johansson
2014-09-24 19:06 ` [PATCH] drivers/soc: ti: fix build break with modules Olof Johansson
2014-09-24 19:32 ` Santosh Shilimkar
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=20140924044317.GB24803@localhost \
--to=olof@lixom.net \
--cc=linux-arm-kernel@lists.infradead.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).