From: Siddharth Vadapalli <s-vadapalli@ti.com>
To: Serge Semin <fancer.lancer@gmail.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
<bhelgaas@google.com>, <lpieralisi@kernel.org>, <robh@kernel.org>,
<kw@linux.com>, <linux-pci@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <r-gunasekaran@ti.com>,
<srk@ti.com>, <s-vadapalli@ti.com>
Subject: Re: [PATCH v3] PCI: keystone: Fix pci_ops for AM654x SoC
Date: Mon, 23 Oct 2023 17:05:30 +0530 [thread overview]
Message-ID: <499a2f6c-3104-492c-be34-3ad286cdf069@ti.com> (raw)
In-Reply-To: <7itgyqntgmjcqh4yk2j76af5h6i6lwpcita7syxxtyi4dhb6up@2qix56u3g4kg>
Serge,
On 23/10/23 16:12, Serge Semin wrote:
...
> Siddharth, if it won't be that much bother and you have an access to
> the v3.65-based Keystone PCIe device, could you please have a look
> whether it's possible to implement what Bjorn suggested? *
Unfortunately I don't have any SoC/Device with me that has the v3.65 PCIe
controller, so I will not be able to test Bjorn's suggestion.
>
> * it's irrespective to this patch. This fix looks good. If Bjorn
> and/or Mani are ok with it, I guess it can be already merged in.
>
> -Serge(y)
>
>>
>> Bjorn
--
Regards,
Siddharth.
WARNING: multiple messages have this Message-ID (diff)
From: Siddharth Vadapalli <s-vadapalli@ti.com>
To: Serge Semin <fancer.lancer@gmail.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
<bhelgaas@google.com>, <lpieralisi@kernel.org>, <robh@kernel.org>,
<kw@linux.com>, <linux-pci@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <r-gunasekaran@ti.com>,
<srk@ti.com>, <s-vadapalli@ti.com>
Subject: Re: [PATCH v3] PCI: keystone: Fix pci_ops for AM654x SoC
Date: Mon, 23 Oct 2023 17:05:30 +0530 [thread overview]
Message-ID: <499a2f6c-3104-492c-be34-3ad286cdf069@ti.com> (raw)
In-Reply-To: <7itgyqntgmjcqh4yk2j76af5h6i6lwpcita7syxxtyi4dhb6up@2qix56u3g4kg>
Serge,
On 23/10/23 16:12, Serge Semin wrote:
...
> Siddharth, if it won't be that much bother and you have an access to
> the v3.65-based Keystone PCIe device, could you please have a look
> whether it's possible to implement what Bjorn suggested? *
Unfortunately I don't have any SoC/Device with me that has the v3.65 PCIe
controller, so I will not be able to test Bjorn's suggestion.
>
> * it's irrespective to this patch. This fix looks good. If Bjorn
> and/or Mani are ok with it, I guess it can be already merged in.
>
> -Serge(y)
>
>>
>> Bjorn
--
Regards,
Siddharth.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-10-23 11:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 8:13 [PATCH v3] PCI: keystone: Fix pci_ops for AM654x SoC Siddharth Vadapalli
2023-10-19 8:13 ` Siddharth Vadapalli
2023-10-19 10:05 ` Serge Semin
2023-10-19 10:05 ` Serge Semin
2023-10-19 22:08 ` Bjorn Helgaas
2023-10-19 22:08 ` Bjorn Helgaas
2023-10-23 10:42 ` Serge Semin
2023-10-23 10:42 ` Serge Semin
2023-10-23 11:35 ` Siddharth Vadapalli [this message]
2023-10-23 11:35 ` Siddharth Vadapalli
2023-10-23 21:26 ` Bjorn Helgaas
2023-10-23 21:26 ` Bjorn Helgaas
2023-10-25 5:02 ` Siddharth Vadapalli
2023-10-25 5:02 ` Siddharth Vadapalli
2023-10-25 10:28 ` Serge Semin
2023-10-25 10:28 ` Serge Semin
2023-10-25 10:58 ` Siddharth Vadapalli
2023-10-25 10:58 ` Siddharth Vadapalli
2023-10-27 8:43 ` Siddharth Vadapalli
2023-10-27 8:43 ` Siddharth Vadapalli
2023-11-15 8:39 ` Siddharth Vadapalli
2023-11-15 8:39 ` Siddharth Vadapalli
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=499a2f6c-3104-492c-be34-3ad286cdf069@ti.com \
--to=s-vadapalli@ti.com \
--cc=bhelgaas@google.com \
--cc=fancer.lancer@gmail.com \
--cc=helgaas@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=r-gunasekaran@ti.com \
--cc=robh@kernel.org \
--cc=srk@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.