From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Hannes Reinecke <hare@suse.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
James Bottomley <james.bottomley@hansenpartnership.com>,
linux-scsi@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCHv6 0/3] Deprecate DAC960 driver
Date: Fri, 19 Oct 2018 18:26:19 -0400 [thread overview]
Message-ID: <yq1in1xinec.fsf@oracle.com> (raw)
In-Reply-To: <d9f916e8-3a7a-f768-72ba-fcadc8e34ec0@suse.de> (Hannes Reinecke's message of "Thu, 18 Oct 2018 07:54:32 +0200")
Hannes,
> No, I haven't, but I should probably do it. Should I fix up the patch
> or send an additional one?
Additional, please.
>> Also, does MODULE_ALIAS do the right thing when a driver is split
>> into two distinct modules?
>>
> Well, it does; half of the time :-)
Is this a qualified guess or have you actually tried?
> Personally, I don't think there'll be many users around so I've just
> added if for completions sake.
Yeah, I agree it's less critical than mpt[23]sas. However, I'm sure
we'll break something for someone somewhere.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2018-10-19 22:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 15:25 [PATCHv6 0/3] Deprecate DAC960 driver Hannes Reinecke
2018-10-17 15:25 ` [PATCH 1/3] myrb: Add Mylex RAID controller (block interface) Hannes Reinecke
2018-10-17 15:25 ` [PATCH 2/3] myrs: Add Mylex RAID controller (SCSI interface) Hannes Reinecke
2018-10-17 15:25 ` [PATCH 3/3] drivers/block: Remove DAC960 driver Hannes Reinecke
2018-10-17 15:43 ` [PATCHv6 0/3] Deprecate " Jens Axboe
2018-10-18 1:14 ` Martin K. Petersen
2018-10-18 5:54 ` Hannes Reinecke
2018-10-19 22:26 ` Martin K. Petersen [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=yq1in1xinec.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@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