netdev - Re: [RFC][PATCH] PCI: Reserve address space for powered-off devices behind PCIe bridges

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:   Thu, 15 Jul 2021 19:49:56 +0000
From:   "Billie Alsup (balsup)" <balsup@...co.com>
To:     Bjorn Helgaas <helgaas@...nel.org>
CC:     Paul Menzel <pmenzel@...gen.mpg.de>,
        Bjorn Helgaas <bhelgaas@...gle.com>,
        Guohan Lu <lguohan@...il.com>,
        "Madhava Reddy Siddareddygari (msiddare)" <msiddare@...co.com>,
        "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "David S. Miller" <davem@...emloft.net>,
        Jakub Kicinski <kuba@...nel.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        Sergey Miroshnichenko <s.miroshnichenko@...ro.com>
Subject: Re: [RFC][PATCH] PCI: Reserve address space for powered-off devices
 behind PCIe bridges



    >On 7/15/21, 11:57 AM, "Bjorn Helgaas" <helgaas@...nel.org> wrote:

    >Since you've gone to that much trouble already, also note
    >http://vger.kernel.org/majordomo-info.html and
    >https://people.kernel.org/tglx/notes-about-netiquette 

My apologies. I was just cc'd on a thread and blindly responded.  
I didn't realize my mistake until receiving bounce messages for the html formatted message.

    >BTW, the attribution in the email you quoted below got corrupted in
    >such a way that it appears that I wrote the whole thing, instead of 
    >what actually happened, which is that I wrote a half dozen lines of
    >response to your email.  Linux uses old skool email conventions ;)

I will pay closer attention next time.  Again, my apologies.
Outlook really is a bad client for these types of emails!