linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: PCI <linux-pci@vger.kernel.org>
Subject: Re: [PATCH v5] PCI: qcom: Use default config space read function
Date: Mon, 1 Apr 2019 12:39:33 +0200	[thread overview]
Message-ID: <891b4d8a-f353-993e-62d1-1c1d3c749b4c@free.fr> (raw)
In-Reply-To: <20190329163808.GB8768@e107981-ln.cambridge.arm.com>

On 29/03/2019 17:38, Lorenzo Pieralisi wrote:

> On Mon, Mar 25, 2019 at 04:42:55PM +0100, Marc Gonzalez wrote:
>
>> Move the device class fudge to a proper fixup function, and remove
>> qcom_pcie_rd_own_conf() which has become useless.
>>
>> NB: dw_pcie_setup_rc() already did the right thing, but it's broken
>> on older qcom chips, such as 8064.
>>
>> Signed-off-by: Marc Gonzalez <marc.w.gonzalez@free.fr>
>> ---
>> Changes from v4 to v5: Apply fixup to all qcom chips, the same way it was before
>> (thus the code remains functionally equivalent)
>> Drop Srinivas' Tested-by tag because of the change
>> ---
>>  drivers/pci/controller/dwc/pcie-qcom.c | 23 ++++++-----------------
>>  1 file changed, 6 insertions(+), 17 deletions(-)
> 
> Applied to pci/dwc for v5.2, thanks.

Thanks!

Do you push to linux-next? (The patch is not in next-20190401)

Regards.

  reply	other threads:[~2019-04-01 10:39 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-11 14:56 [RFC PATCH v1] PCI: qcom: Use quirk to override incorrect device class Marc Gonzalez
2019-03-12 12:42 ` Stanimir Varbanov
2019-03-12 17:18   ` Marc Gonzalez
2019-03-12 17:34     ` Marc Gonzalez
2019-03-13 11:45       ` [PATCH v2] PCI: qcom: Use default config space read function Marc Gonzalez
2019-03-13 13:13         ` Marc Gonzalez
2019-03-13 18:29         ` Srinivas Kandagatla
2019-03-13 20:39           ` Marc Gonzalez
2019-03-13 21:52             ` Srinivas Kandagatla
2019-03-13 22:26               ` Marc Gonzalez
2019-03-14 11:10                 ` Srinivas Kandagatla
2019-03-14 13:18                   ` Marc Gonzalez
2019-03-18 14:28                     ` [PATCH v3] " Marc Gonzalez
2019-03-18 14:39                       ` Srinivas Kandagatla
2019-03-18 16:35                       ` Stanimir Varbanov
2019-03-18 17:14                         ` [PATCH v4] " Marc Gonzalez
2019-03-25 12:11                           ` Marc Gonzalez
2019-03-25 13:32                             ` Stanimir Varbanov
2019-03-25 15:42                               ` [PATCH v5] " Marc Gonzalez
2019-03-29 13:48                                 ` Marc Gonzalez
2019-03-29 15:55                                 ` Stanimir Varbanov
2019-03-29 16:38                                 ` Lorenzo Pieralisi
2019-04-01 10:39                                   ` Marc Gonzalez [this message]
2019-04-01 11:12                                     ` Lorenzo Pieralisi
2019-04-30 14:06       ` [RFC PATCH v1] PCI: qcom: Use quirk to override incorrect device class Lorenzo Pieralisi
2019-05-02  9:42         ` Marc Gonzalez

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=891b4d8a-f353-993e-62d1-1c1d3c749b4c@free.fr \
    --to=marc.w.gonzalez@free.fr \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.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).