From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: Bart Van Assche <bvanassche@acm.org>,
Jens Axboe <axboe@kernel.dk>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
James Bottomley <james.bottomley@hansenpartnership.com>,
Christoph Hellwig <hch@lst.de>,
linux-block@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCHv4 0/3] Deprecate DAC960 driver
Date: Wed, 10 Oct 2018 07:56:37 +0200 [thread overview]
Message-ID: <20181010055637.GA12844@lst.de> (raw)
In-Reply-To: <9c44c367-6854-f74d-8317-f0ce5ad64cca@suse.de>
On Wed, Oct 10, 2018 at 07:49:03AM +0200, Hannes Reinecke wrote:
> On 10/10/18 4:03 AM, Bart Van Assche wrote:
>> On 10/9/18 8:26 AM, Hannes Reinecke wrote:
>>> as we're trying to get rid of the remaining request_fn drivers here's
>>> a patchset to move the DAC960 driver to the SCSI stack.
>>> As per request from hch I've split up the driver into two new SCSI
>>> drivers called 'myrb' and 'myrs'.
>>
>> Hi Hannes,
>>
>> It seems like only patches 1/3 and 2/3 but not 3/3 made it to the list?
>> See e.g. https://marc.info/?a=105878808800002&r=1.
>>
> Hmm.
>
> I have them in my inbox, and all patches have the same recipients.
> Care to re-check?
I got them all, but 1 had a major, major delay in my inbox.
In my linux-scsi box 3/3 is missing.
next prev parent reply other threads:[~2018-10-10 5:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 15:26 [PATCHv4 0/3] Deprecate DAC960 driver Hannes Reinecke
2018-10-09 15:26 ` [PATCH 1/3] myrb: Add Mylex RAID controller (block interface) Hannes Reinecke
2018-10-10 12:56 ` Christoph Hellwig
2018-10-09 15:27 ` [PATCH 2/3] myrs: Add Mylex RAID controller (SCSI interface) Hannes Reinecke
2018-10-09 15:27 ` [PATCH 3/3] drivers/block: Remove DAC960 driver Hannes Reinecke
2018-10-10 2:03 ` [PATCHv4 0/3] Deprecate " Bart Van Assche
2018-10-10 5:49 ` Hannes Reinecke
2018-10-10 5:56 ` Christoph Hellwig [this message]
2018-10-10 13:52 ` Bart Van Assche
2018-10-11 2:51 ` Martin K. Petersen
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=20181010055637.GA12844@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hare@suse.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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 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.