Linux block layer
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@lst.de>, tglx@linutronix.de
Cc: axboe@kernel.dk, linux-block@vger.kernel.org,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] blk-mq: add a first_vec argument to blk_mq_pci_map_queues
Date: Mon, 7 Nov 2016 10:37:16 +0100	[thread overview]
Message-ID: <c9322061-cbd0-8347-6581-d0a91c8b144f@suse.de> (raw)
In-Reply-To: <1478473646-12524-3-git-send-email-hch@lst.de>

On 11/07/2016 12:07 AM, Christoph Hellwig wrote:
> This allows skipping the first N IRQ vectors in case they are used for
> control or admin interrupts.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>  block/blk-mq-pci.c         | 6 ++++--
>  drivers/nvme/host/pci.c    | 2 +-
>  include/linux/blk-mq-pci.h | 3 ++-
>  3 files changed, 7 insertions(+), 4 deletions(-)
> 
With this patch smartpqi doesn't compile anymore; it still uses the old
interface.
So to get this merged you probably should send a patch for that one, too.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		   Teamlead Storage & Networking
hare@suse.de			               +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N�rnberg
GF: F. Imend�rffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG N�rnberg)

  parent reply	other threads:[~2016-11-07  9:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-06 23:07 support for partial irq affinity assignment Christoph Hellwig
2016-11-06 23:07 ` [PATCH 1/2] irq,pci: allow drivers to specify complex affinity requirement Christoph Hellwig
2016-11-07  8:36   ` Hannes Reinecke
2016-11-07 15:53   ` Thomas Gleixner
2016-11-06 23:07 ` [PATCH 2/2] blk-mq: add a first_vec argument to blk_mq_pci_map_queues Christoph Hellwig
2016-11-07  8:37   ` Hannes Reinecke
2016-11-07  9:37   ` Hannes Reinecke [this message]
2016-11-07 14:46     ` Christoph Hellwig

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=c9322061-cbd0-8347-6581-d0a91c8b144f@suse.de \
    --to=hare@suse.de \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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