The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Vikash Bansal <bvikas@vmware.com>
To: "srivatsa@csail.mit.edu" <srivatsa@csail.mit.edu>,
	Bjorn Helgaas <helgaas@kernel.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	"bhelgaas@google.com" <bhelgaas@google.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Srivatsa Bhat <srivatsab@vmware.com>,
	Alexey Makhalov <amakhalov@vmware.com>,
	Srinidhi Rao <srinidhir@vmware.com>,
	Anish Swaminathan <anishs@vmware.com>,
	Vasavi Sirnapalli <vsirnapalli@vmware.com>,
	Ajay Kaher <akaher@vmware.com>
Subject: Re: [PATCH] PCI: Speed up device init by parsing capabilities all at once
Date: Sat, 22 Jan 2022 18:51:46 +0000	[thread overview]
Message-ID: <808EC731-7175-4DD4-A7D7-CFC3A9856A7D@vmware.com> (raw)
In-Reply-To: <d1b71a67-80aa-629c-6aff-7265036fffe7@csail.mit.edu>

    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@csail.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@linuxfoundation.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@vger.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&amp;data=04%7C01%7Cbvikas%40vmware.com%7Caeeecd0515704520558208d9dd4cb350%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637784143774862668%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=DeEhueGnvJRTeavdK86HO2cSDEwWh7DLTte%2F4P00alA%3D&amp;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&amp;data=04%7C01%7Cbvikas%40vmware.com%7Caeeecd0515704520558208d9dd4cb350%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637784143774862668%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=iTMr0mSNFph6AWMohfyCGxM6rVwXTjUQ5QW29bhecMQ%3D&amp;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


      reply	other threads:[~2022-01-22 18:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1642526161-22499-1-git-send-email-bvikas@vmware.com>
2022-01-20  6:26 ` [PATCH] PCI: Speed up device init by parsing capabilities all at once Greg KH
2022-01-20 17:31   ` Vikash Bansal
2022-01-22 19:09     ` Vikash Bansal
2022-01-21 17:26   ` Vikash Bansal
2022-01-21 19:42     ` Bjorn Helgaas
2022-01-22  2:12       ` Srivatsa S. Bhat
2022-01-22 18:51         ` Vikash Bansal [this message]

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=808EC731-7175-4DD4-A7D7-CFC3A9856A7D@vmware.com \
    --to=bvikas@vmware.com \
    --cc=akaher@vmware.com \
    --cc=amakhalov@vmware.com \
    --cc=anishs@vmware.com \
    --cc=bhelgaas@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=helgaas@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=srinidhir@vmware.com \
    --cc=srivatsa@csail.mit.edu \
    --cc=srivatsab@vmware.com \
    --cc=vsirnapalli@vmware.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