From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Juergen Gross <jgross@suse.com>, Jens Axboe <axboe@kernel.dk>,
linux-scsi@vger.kernel.org,
"Martin K. Petersen" <martin.petersen@oracle.com>,
netdev@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
target-devel@vger.kernel.org, kvm@vger.kernel.org,
qla2xxx-upstream@qlogic.com,
linux1394-devel@lists.sourceforge.net,
Kent Overstreet <kent.overstreet@gmail.com>
Subject: Re: [PATCH 0/3] Use sbitmap instead of percpu_ida
Date: Mon, 18 Jun 2018 22:26:13 -0400 [thread overview]
Message-ID: <yq1bmc7ikai.fsf@oracle.com> (raw)
In-Reply-To: <20180615023731.GA5706@bombadil.infradead.org> (Matthew Wilcox's message of "Thu, 14 Jun 2018 19:37:31 -0700")
Matthew,
>> Since most of the changes are in scsi or target, should I take this
>> series through my tree?
>
> I'd welcome that. Nick seems to be inactive as target maintainer;
> his tree on kernel.org hasn't seen any updates in five months.
Applied to 4.19/scsi-queue, thanks!
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Juergen Gross <jgross@suse.com>, Jens Axboe <axboe@kernel.dk>,
linux-scsi@vger.kernel.org,
"Martin K. Petersen" <martin.petersen@oracle.com>,
netdev@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
target-devel@vger.kernel.org, kvm@vger.kernel.org,
qla2xxx-upstream@qlogic.com,
linux1394-devel@lists.sourceforge.net,
Kent Overstreet <kent.overstreet@gmail.com>
Subject: Re: [PATCH 0/3] Use sbitmap instead of percpu_ida
Date: Tue, 19 Jun 2018 02:26:13 +0000 [thread overview]
Message-ID: <yq1bmc7ikai.fsf@oracle.com> (raw)
In-Reply-To: <20180615023731.GA5706@bombadil.infradead.org> (Matthew Wilcox's message of "Thu, 14 Jun 2018 19:37:31 -0700")
Matthew,
>> Since most of the changes are in scsi or target, should I take this
>> series through my tree?
>
> I'd welcome that. Nick seems to be inactive as target maintainer;
> his tree on kernel.org hasn't seen any updates in five months.
Applied to 4.19/scsi-queue, thanks!
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
target-devel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net, linux-usb@vger.kernel.org,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, Juergen Gross <jgross@suse.com>,
qla2xxx-upstream@qlogic.com,
Kent Overstreet <kent.overstreet@gmail.com>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH 0/3] Use sbitmap instead of percpu_ida
Date: Mon, 18 Jun 2018 22:26:13 -0400 [thread overview]
Message-ID: <yq1bmc7ikai.fsf@oracle.com> (raw)
In-Reply-To: <20180615023731.GA5706@bombadil.infradead.org> (Matthew Wilcox's message of "Thu, 14 Jun 2018 19:37:31 -0700")
Matthew,
>> Since most of the changes are in scsi or target, should I take this
>> series through my tree?
>
> I'd welcome that. Nick seems to be inactive as target maintainer;
> his tree on kernel.org hasn't seen any updates in five months.
Applied to 4.19/scsi-queue, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2018-06-19 2:26 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 19:05 [PATCH 0/3] Use sbitmap instead of percpu_ida Matthew Wilcox
2018-06-12 19:05 ` Matthew Wilcox
2018-06-12 19:05 ` [PATCH 1/3] target: Abstract tag freeing Matthew Wilcox
2018-06-12 19:05 ` Matthew Wilcox
2018-06-12 19:05 ` Matthew Wilcox
2018-06-12 19:05 ` [1/3] " Matthew Wilcox
2018-06-12 19:05 ` [PATCH 1/3] " Matthew Wilcox
2018-06-12 19:05 ` [PATCH 2/3] Convert target drivers to use sbitmap Matthew Wilcox
2018-06-12 19:05 ` Matthew Wilcox
2018-06-12 19:05 ` Matthew Wilcox
2018-06-12 19:05 ` Matthew Wilcox
2018-06-12 19:05 ` [2/3] " Matthew Wilcox
2018-06-12 19:05 ` [PATCH 3/3] Remove percpu_ida Matthew Wilcox
2018-06-12 19:05 ` Matthew Wilcox
2018-06-12 19:05 ` Matthew Wilcox
2018-06-12 19:05 ` [3/3] " Matthew Wilcox
2018-06-12 19:05 ` [PATCH 3/3] " Matthew Wilcox
2018-06-12 20:06 ` [PATCH 0/3] Use sbitmap instead of percpu_ida Bart Van Assche
2018-06-12 20:06 ` Bart Van Assche
2018-06-12 20:40 ` Jens Axboe
2018-06-12 20:40 ` Jens Axboe
2018-06-15 2:06 ` Martin K. Petersen
2018-06-15 2:06 ` Martin K. Petersen
2018-06-15 2:06 ` Martin K. Petersen
2018-06-15 2:37 ` Matthew Wilcox
2018-06-15 2:37 ` Matthew Wilcox
2018-06-15 2:37 ` Matthew Wilcox
2018-06-19 2:26 ` Martin K. Petersen [this message]
2018-06-19 2:26 ` Martin K. Petersen
2018-06-19 2:26 ` Martin K. Petersen
2018-06-15 7:37 ` Christoph Hellwig
2018-06-15 7:37 ` Christoph Hellwig
2018-06-15 7:37 ` 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=yq1bmc7ikai.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=axboe@kernel.dk \
--cc=jgross@suse.com \
--cc=kent.overstreet@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=qla2xxx-upstream@qlogic.com \
--cc=target-devel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.