linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Billie Alsup (balsup)" <balsup@cisco.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Guohan Lu <lguohan@gmail.com>,
	"Madhava Reddy Siddareddygari (msiddare)" <msiddare@cisco.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Sergey Miroshnichenko <s.miroshnichenko@yadro.com>
Subject: Re: [RFC][PATCH] PCI: Reserve address space for powered-off devices behind PCIe bridges
Date: Thu, 15 Jul 2021 19:49:56 +0000	[thread overview]
Message-ID: <0480940E-F7B9-4EE3-B666-5AD490788198@cisco.com> (raw)
In-Reply-To: <20210715185649.GA1984276@bjorn-Precision-5520>



    >On 7/15/21, 11:57 AM, "Bjorn Helgaas" <helgaas@kernel.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!


  reply	other threads:[~2021-07-15 19:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BYAPR11MB3527AEB1E4969C0833D1697ED9129@BYAPR11MB3527.namprd11.prod.outlook.com>
2021-07-15 17:13 ` [RFC][PATCH] PCI: Reserve address space for powered-off devices behind PCIe bridges Bjorn Helgaas
2021-07-15 18:12   ` Billie Alsup (balsup)
2021-07-15 18:56     ` Bjorn Helgaas
2021-07-15 19:49       ` Billie Alsup (balsup) [this message]
2021-07-15 19:56         ` Bjorn Helgaas
2021-07-13  7:31 [PATCH] " Paul Menzel
2021-07-15 13:50 ` [RFC][PATCH] " Paul Menzel
2021-07-15 14:07   ` 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=0480940E-F7B9-4EE3-B666-5AD490788198@cisco.com \
    --to=balsup@cisco.com \
    --cc=bhelgaas@google.com \
    --cc=davem@davemloft.net \
    --cc=helgaas@kernel.org \
    --cc=kuba@kernel.org \
    --cc=lguohan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=msiddare@cisco.com \
    --cc=netdev@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=s.miroshnichenko@yadro.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;
as well as URLs for NNTP newsgroup(s).