public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Sreekanth.Reddy@avagotech.com, hch@lst.de, hare@suse.de,
	linux-kernel@vger.kernel.org,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: MPT2SAS boot fail... due to silently loosing the driver
Date: Mon, 30 Nov 2015 09:27:32 -0800	[thread overview]
Message-ID: <1448904452.2204.24.camel@HansenPartnership.com> (raw)
In-Reply-To: <yq14mg3iesi.fsf@sermon.lab.mkp.net>

[cc to linux-scsi added]
On Mon, 2015-11-30 at 12:21 -0500, Martin K. Petersen wrote:
> >>>>> "Ingo" == Ingo Molnar <mingo@kernel.org> writes:
> 
> Ingo> So you need to make it interactive, with a short help text that
> Ingo> explains to users that this is legacy option only, and that they
> Ingo> should enable the MPT3SAS option if they want to configure things
> Ingo> manually.
> 
> +config SCSI_MPT2SAS
> +	tristate "Legacy MPT2SAS config option"
> +	default n
> +	select SCSI_MPT3SAS
> +	---help---
> +	Dummy config option for backwards compatiblity: configure the MPT3SAS 
> +	driver instead.
> 
> That's fine with me.
> 
> Sreekanth/Christoph/James: Any objections?

Looks OK, we probably need a removal timeframe for it as well.  What
about removal in 4.6?

James




  parent reply	other threads:[~2015-11-30 17:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 12:46 MPT2SAS boot fail... due to silently loosing the driver Peter Zijlstra
2015-11-24  7:51 ` Christoph Hellwig
2015-11-24  7:54   ` Hannes Reinecke
2015-11-24  7:56     ` Christoph Hellwig
2015-11-24  8:04   ` Ingo Molnar
2015-11-24 12:02 ` Martin K. Petersen
2015-11-26 10:48   ` Ingo Molnar
2015-11-30 17:21     ` Martin K. Petersen
2015-11-30 17:24       ` Christoph Hellwig
2015-11-30 17:27       ` James Bottomley [this message]
2015-12-01  9:49       ` Sreekanth Reddy
2015-12-02  9:57       ` Ingo Molnar
2015-11-26 10:51   ` Ingo Molnar

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=1448904452.2204.24.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=Sreekanth.Reddy@avagotech.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=mingo@kernel.org \
    --cc=peterz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox