lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 21 Jan 2022 18:12:50 -0800
From:   "Srivatsa S. Bhat" <srivatsa@...il.mit.edu>
To:     Bjorn Helgaas <helgaas@...nel.org>,
        Vikash Bansal <bvikas@...are.com>
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

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
> http://vger.kernel.org/majordomo-info.html)?
> 
> It doesn't appear in the thread at
> https://lore.kernel.org/all/7E2C2648-76CE-4987-AB4F-7B4576F10D7B@vmware.com/ 
> 

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ