[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <808EC731-7175-4DD4-A7D7-CFC3A9856A7D@vmware.com>
Date: Sat, 22 Jan 2022 18:51:46 +0000
From: Vikash Bansal <bvikas@...are.com>
To: "srivatsa@...il.mit.edu" <srivatsa@...il.mit.edu>,
Bjorn Helgaas <helgaas@...nel.org>
CC: Greg KH <gregkh@...uxfoundation.org>,
"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Srivatsa Bhat <srivatsab@...are.com>,
Alexey Makhalov <amakhalov@...are.com>,
Srinidhi Rao <srinidhir@...are.com>,
Anish Swaminathan <anishs@...are.com>,
Vasavi Sirnapalli <vsirnapalli@...are.com>,
Ajay Kaher <akaher@...are.com>
Subject: Re: [PATCH] PCI: Speed up device init by parsing capabilities all at
once
Thanks Srivatsa for clarification, even I am surprised to see this.
I will send V2 of the patch, hopefully that should appear in the thread.
On 22/01/22, 7:42 AM, "Srivatsa S. Bhat" <srivatsa@...il.mit.edu> wrote:
>
>Hi Bjorn,
>
>On 1/21/22 11:42 AM, Bjorn Helgaas wrote:
>> On Fri, Jan 21, 2022 at 05:26:35PM +0000, Vikash Bansal wrote:
>>> On 20/01/22, 11:56 AM, "Greg KH" <gregkh@...uxfoundation.org> wrote:
>>>
>>> Run pahole for pci_dev structure, it is not adding any padding bytes.
>>> Please refer to my previous email for replies to Greg's other comments.
>>
>> Please don't indent your entire response. The original posting
>> apparently didn't go to linux-pci@...r.kernel.org or was rejected,
>> maybe because it wasn't plain text (see
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvger.kernel.org%2Fmajordomo-info.html&data=04%7C01%7Cbvikas%40vmware.com%7Caeeecd0515704520558208d9dd4cb350%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637784143774862668%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=DeEhueGnvJRTeavdK86HO2cSDEwWh7DLTte%2F4P00alA%3D&reserved=0)?
>>
>> It doesn't appear in the thread at
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore.kernel.org%2Fall%2F7E2C2648-76CE-4987-AB4F-7B4576F10D7B%40vmware.com%2F&data=04%7C01%7Cbvikas%40vmware.com%7Caeeecd0515704520558208d9dd4cb350%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637784143774862668%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=iTMr0mSNFph6AWMohfyCGxM6rVwXTjUQ5QW29bhecMQ%3D&reserved=0
>>
>
>Looking at the source for Vikash's first email in this thread, I see:
>"Content-Type: text/plain", so I don't think that was the issue. Also,
>the patch was sent using git-send-email: "X-Mailer: git-send-email
>2.6.2".
>
>Is there a way to find out exactly why that email might have prompted
>the mailing list to drop it?
>
>Thank you!
>
>Regards,
>Srivatsa
>VMware Photon OS
Powered by blists - more mailing lists