public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
To: Alexey Kardashevskiy <aik@amd.com>,
	Sathyanarayanan Kuppuswamy Natarajan
	<sathyanarayanan.nkuppuswamy@gmail.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bjorn Helgaas <bhelgaas@google.com>,
	Ira Weiny <ira.weiny@intel.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Lukas Wunner <lukas@wunner.de>
Subject: Re: [PATCH kernel v3] PCI/DOE: Support discovery version 2
Date: Wed, 13 Mar 2024 23:49:22 -0700	[thread overview]
Message-ID: <8d076ed4-5c3c-499a-bca0-9bd51d5454cc@linux.intel.com> (raw)
In-Reply-To: <8d542410-d8e1-4243-939c-6ce7743a66f1@amd.com>


On 3/13/24 5:59 PM, Alexey Kardashevskiy wrote:
>
>
> On 7/3/24 17:22, Sathyanarayanan Kuppuswamy Natarajan wrote:
>> On Wed, Mar 6, 2024 at 10:09 PM Alexey Kardashevskiy <aik@amd.com> wrote:
>>>
>>>
>>>
>>> On 7/3/24 16:06, Kuppuswamy Sathyanarayanan wrote:
>>>>
>>>> On 3/6/24 6:20 PM, Alexey Kardashevskiy wrote:
>>>>> PCIe r6.1, sec 6.30.1.1 defines a "DOE Discovery Version" field in
>>>>> the DOE Discovery Request Data Object Contents (3rd DW) as:
>>>>>
>>>>> 15:8 DOE Discovery Version – must be 02h if the Capability Version in
>>>>> the Data Object Exchange Extended Capability is 02h or greater.
>>>>
>>>> Does this change fix any functional issue? If yes, please add Fixes:
>>>> tag and probably CC stable?
>>>
>>> The issue is that before this patch the DOE driver was following PCIe
>>> r6.0 and it was not working on a device with DOE cap v2 added in r6.1.
>>> Is it "fixes"?
>>>
>>
>> Since you are enabling support for the newer spec version, I think it will not
>> fall under bug fix. But it might be qualified for the stable branch.
>> It depends on
>> whether you want to support this device in older(stable) kernels.
>
>
> I am going to need lot more stuff (TSM, IDE, TDISP) in addition to this but it is coming much later so there is no point in pushing this alone to older kernels. Thanks,
>
>
Got it.

Reviewed-by: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>


-- 
Sathyanarayanan Kuppuswamy
Linux Kernel Developer


  reply	other threads:[~2024-03-14  6:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07  2:20 [PATCH kernel v3] PCI/DOE: Support discovery version 2 Alexey Kardashevskiy
2024-03-07  5:06 ` Kuppuswamy Sathyanarayanan
2024-03-07  6:09   ` Alexey Kardashevskiy
2024-03-07  6:22     ` Sathyanarayanan Kuppuswamy Natarajan
2024-03-14  0:59       ` Alexey Kardashevskiy
2024-03-14  6:49         ` Kuppuswamy Sathyanarayanan [this message]
2024-04-09  8:25           ` Alexey Kardashevskiy
2024-04-09 14:33 ` Bjorn Helgaas

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=8d076ed4-5c3c-499a-bca0-9bd51d5454cc@linux.intel.com \
    --to=sathyanarayanan.kuppuswamy@linux.intel.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=aik@amd.com \
    --cc=bhelgaas@google.com \
    --cc=dan.j.williams@intel.com \
    --cc=ira.weiny@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=sathyanarayanan.nkuppuswamy@gmail.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