linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: santosh.shilimkar@gmail.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Enable PCI controller for Keystone SoCs
Date: Tue, 28 Oct 2014 09:33:04 -0700	[thread overview]
Message-ID: <544FC540.1050501@gmail.com> (raw)
In-Reply-To: <544FBF4D.6000502@ti.com>



On 10/28/2014 09:07 AM, Murali Karicheri wrote:
> On 10/28/2014 12:06 PM, Murali Karicheri wrote:
>> On 10/24/2014 01:51 PM, Murali Karicheri wrote:
>>> Now that Keystone PCI driver is merged to v3.18, this patch series
>>> add build options and DTS bindings to enable the driver for Keystone
>>> SoCs.
>>>
>>> CC : Santosh Shilimkar<santosh.shilimkar@gmail.com>
>>> CC : Greg Kroah-Hartman<gregkh@linuxfoundation.org>
>>> CC : Rob Herring<robh+dt@kernel.org>
>>> CC : Pawel Moll<pawel.moll@arm.com>
>>> CC : Mark Rutland<mark.rutland@arm.com>
>>> CC : Ian Campbell<ijc+devicetree@hellion.org.uk>
>>> CC : Kumar Gala<galak@codeaurora.org>
>>> CC : Russell King<linux@arm.linux.org.uk>
>>> CC : devicetree at vger.kernel.org
>>>
>>> Murali Karicheri (4):
>>> ARM: keystone: add pcie related options
>>> ARM: keystone: defconfig: add options to enable PCI controller
>>> ARM: keystone: dts: add DT bindings for PCI controller for port 0
>>> ARM: keystone: dts: add DT bindings for PCI controller for port 1
>>>
>>> arch/arm/boot/dts/k2e.dtsi | 45 +++++++++++++++++++++++++++++++++++
>>> arch/arm/boot/dts/keystone.dtsi | 45 +++++++++++++++++++++++++++++++++++
>>> arch/arm/configs/keystone_defconfig | 3 +++
>>> arch/arm/mach-keystone/Kconfig | 2 ++
>>> 4 files changed, 95 insertions(+)
>>>
>> Santosh,
>>
>> Could you review this and apply to your tree for merge by end of this
>> week if this looks good and there are no comments?
>>
> Adding Santosh's personal email ID
>
Just use the listed kernel.org id while posting patches which needs
my attention. Please repost the series again so that I have all the
patches.

Also what happened with the PCIE notifier related series ?
If you have already proposed something, please loop me on the thread.

Thanks and Regards,
Santosh

  reply	other threads:[~2014-10-28 16:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24 17:51 [PATCH 0/4] Enable PCI controller for Keystone SoCs Murali Karicheri
2014-10-24 17:51 ` [PATCH 1/4] ARM: keystone: add pcie related options Murali Karicheri
2014-10-24 17:51 ` [PATCH 2/4] ARM: keystone: defconfig: add options to enable PCI controller Murali Karicheri
2014-10-24 17:51 ` [PATCH 3/4] ARM: keystone: dts: add DT bindings for PCI controller for port 0 Murali Karicheri
2014-10-24 17:51 ` [PATCH 4/4] ARM: keystone: dts: add DT bindings for PCI controller for port 1 Murali Karicheri
2014-10-28 16:06 ` [PATCH 0/4] Enable PCI controller for Keystone SoCs Murali Karicheri
2014-10-28 16:07   ` Murali Karicheri
2014-10-28 16:33     ` Santosh Shilimkar [this message]
2014-10-29 15:02       ` Murali Karicheri
2014-10-29 18:56         ` 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=544FC540.1050501@gmail.com \
    --to=santosh.shilimkar@gmail.com \
    --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).