linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rajat Jain <rajatja@google.com>
To: linux-pci <linux-pci@vger.kernel.org>,
	"Boris V." <borisvk@bstnet.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Bjorn Helgaas <helgaas@kernel.org>
Cc: Rajat Jain <rajatxjain@gmail.com>
Subject: Re: [PATCH] PCI: Always call pci_enable_acs() regardless of pdev->acs_cap
Date: Wed, 28 Oct 2020 16:19:17 -0700	[thread overview]
Message-ID: <CACK8Z6HHP7O96zAHW4MM6ZtH-6h1WcJ=VtAVCXbGnRL3400SLA@mail.gmail.com> (raw)
In-Reply-To: <20201028231545.4116866-1-rajatja@google.com>

-random email address (typo)

  reply	other threads:[~2020-10-28 23:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28 23:15 Rajat Jain
2020-10-28 23:19 ` Rajat Jain [this message]
2020-10-30 19:25 ` Alex Williamson
2020-10-30 21:42 ` 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='CACK8Z6HHP7O96zAHW4MM6ZtH-6h1WcJ=VtAVCXbGnRL3400SLA@mail.gmail.com' \
    --to=rajatja@google.com \
    --cc=borisvk@bstnet.org \
    --cc=helgaas@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rajatxjain@gmail.com \
    --subject='Re: [PATCH] PCI: Always call pci_enable_acs() regardless of pdev->acs_cap' \
    /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

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).