linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kishon Vijay Abraham I <kishon@ti.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>, <linux-omap@vger.kernel.org>,
	<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<nsekhar@ti.com>
Subject: Re: [PATCH v2 0/3] PCI: designware/dra7xx: misc fixes and cleanups
Date: Thu, 12 Jan 2017 18:53:41 +0530	[thread overview]
Message-ID: <5877835D.80508@ti.com> (raw)
In-Reply-To: <20170112131552.GA23045@bhelgaas-glaptop.roam.corp.google.com>

Hi,

On Thursday 12 January 2017 06:45 PM, Bjorn Helgaas wrote:
> On Thu, Jan 12, 2017 at 10:52:56AM +0530, Kishon Vijay Abraham I wrote:
>> Hi Bjorn,
>>
>> On Thursday 12 January 2017 02:51 AM, Bjorn Helgaas wrote:
>>> On Fri, Dec 30, 2016 at 03:26:11PM +0530, Kishon Vijay Abraham I wrote:
>>>> This series contains
>>>>         *) a patch to cleanup dra7xx probe
>>>>         *) a patch to force DRA7xx controller to work in GEN1 mode
>>>>         *) a patch to fix dra7xx driver so that even if CONFIG_PCI_MSI
>>>>            is enabled, dra7xx driver can service legacy interrupts
>>>>            (provided the device support only legacy interrupts).
>>>>
>>>> Changes from v1:
>>>> *) rebased to 4.10-rc1 (and [1])
>>>> *) use existing dt property "max-link-speed" instead of creating a new
>>>>    TI specific dt property.
>>>>
>>>> [1] -> https://lkml.org/lkml/2016/12/28/34
>>>>
>>>> Kishon Vijay Abraham I (3):
>>>>   PCI: dra7xx: simplify the probe code
>>>>   PCI: dra7xx: Add support to force RC to work in GEN1 mode
>>>>   PCI: dra7xx: Enable MSI and legacy interrupts simultaneously
>>>>
>>>>  drivers/pci/controller/pci-dra7xx.c |   81 ++++++++++++++++++++---------------
>>>>  1 file changed, 47 insertions(+), 34 deletions(-)
>>>
>>> Applied to pci/host-dra7xx for v4.11.  I haven't applied the directory
>>> rename yet, so I'll fix that up as necessary.
>>
>> I'd have liked that to be merged as well. Is that because Arnd hasn't Acked
>> that one yet?
> 
> Nope, I expect to do the rename in some form.  I'm just trying to
> clear out the easy stuff first before moving on to the harder patches
> in the queue.

cool, thanks. Let me know if I have to resend the patches based on one of your
branches (i.e after you apply the easy stuff).

Thanks
Kishon

  reply	other threads:[~2017-01-12 16:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-30  9:56 [PATCH v2 0/3] PCI: designware/dra7xx: misc fixes and cleanups Kishon Vijay Abraham I
2016-12-30  9:56 ` [PATCH v2 1/3] PCI: dra7xx: simplify the probe code Kishon Vijay Abraham I
2016-12-30  9:56 ` [PATCH v2 2/3] PCI: dra7xx: Add support to force RC to work in GEN1 mode Kishon Vijay Abraham I
2016-12-30  9:56 ` [PATCH v2 3/3] PCI: dra7xx: Enable MSI and legacy interrupts simultaneously Kishon Vijay Abraham I
2017-01-11 21:21 ` [PATCH v2 0/3] PCI: designware/dra7xx: misc fixes and cleanups Bjorn Helgaas
2017-01-12  5:22   ` Kishon Vijay Abraham I
2017-01-12 13:15     ` Bjorn Helgaas
2017-01-12 13:23       ` Kishon Vijay Abraham I [this message]
2017-01-12 13:40         ` Kishon Vijay Abraham I

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=5877835D.80508@ti.com \
    --to=kishon@ti.com \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=nsekhar@ti.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).