linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Keith Busch <keith.busch@intel.com>
To: Jon Derrick <jonathan.derrick@intel.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>, linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI/VMD: Use local SRCU to prevent delaying global RCU
Date: Fri, 11 Nov 2016 16:25:24 -0500	[thread overview]
Message-ID: <20161111212523.GB10660@localhost.localdomain> (raw)
In-Reply-To: <20161111211223.GA2828@localhost.localdomain>

On Fri, Nov 11, 2016 at 02:12:24PM -0700, Jon Derrick wrote:
> Hi Bjorn,
> 
> I need to attach a patch which selects SRCU in the Kconfig. Do you want
> this and the original patch as a new set or should I just send this new
> Kconfig patch?

Hi Jon,
Please send a new patch. This hasn't been applied yet, so we'd prefer
not to have intermediate breakage if we discover the gaps early.

      reply	other threads:[~2016-11-11 21:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-06 22:47 [PATCH] PCI/VMD: Use local SRCU to prevent delaying global RCU Jon Derrick
2016-11-11 21:07 ` Bjorn Helgaas
2016-11-11 21:12   ` Jon Derrick
2016-11-11 21:25     ` Keith Busch [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=20161111212523.GB10660@localhost.localdomain \
    --to=keith.busch@intel.com \
    --cc=helgaas@kernel.org \
    --cc=jonathan.derrick@intel.com \
    --cc=linux-pci@vger.kernel.org \
    /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).