From: Jens Axboe <axboe@kernel.dk>
To: "Miller, Mike (OS Dev)" <Mike.Miller@hp.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: LKML-scsi <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] remove cpqarray from mainline kernel
Date: Fri, 18 Oct 2013 10:55:09 -0600 [thread overview]
Message-ID: <526167ED.1010503@kernel.dk> (raw)
In-Reply-To: <48275AD710FCA34184C2B6186B4016B32D15F735@G6W2491.americas.hpqcorp.net>
On 10/18/2013 10:22 AM, Miller, Mike (OS Dev) wrote:
>
>
>> -----Original Message-----
>> From: Jens Axboe [mailto:axboe@kernel.dk]
>> Sent: Thursday, October 17, 2013 5:36 PM
>> To: Andrew Morton
>> Cc: Miller, Mike (OS Dev); LKML-scsi; LKML
>> Subject: Re: [PATCH 1/1] remove cpqarray from mainline kernel
>>
>> On Thu, Oct 17 2013, Andrew Morton wrote:
>>> On Thu, 17 Oct 2013 12:52:26 -0500 Mike Miller <mike.miller@hp.com>
>> wrote:
>>>
>>>> cpqarray hasn't been used in over 12 years. It's doubtful that
>>>> anyone still uses the board. It's time the driver was removed from the
>> mainline kernel.
>>>> The only updates these days are minor and mostly done by people
>> outside of HP.
>>>
>>> It's amazing the weird stuff people get up to. Perhaps we should
>>> disable it in config for a cycle or two, see if that flushes anyone out?
>>
>> I think that would be prudent, you never know what people run...
>>
>> --
>> Jens Axboe
>
> I agree with Andrew's suggestion. Should I submit a patch that only removes cpqarray from config?
I put one in yesterday:
http://git.kernel.dk/?p=linux-block.git;a=commit;h=f504954db0ecccaded5397e3432cdaf7175602fb
--
Jens Axboe
next prev parent reply other threads:[~2013-10-18 16:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 17:52 [PATCH 1/1] remove cpqarray from mainline kernel Mike Miller
2013-10-17 21:13 ` Andrew Morton
2013-10-17 22:36 ` Jens Axboe
2013-10-18 16:22 ` Miller, Mike (OS Dev)
2013-10-18 16:55 ` Jens Axboe [this message]
2013-10-18 16:57 ` Miller, Mike (OS Dev)
2013-10-18 5:52 ` Hannes Reinecke
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=526167ED.1010503@kernel.dk \
--to=axboe@kernel.dk \
--cc=Mike.Miller@hp.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@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