Re: MPT2SAS boot fail... due to silently loosing the driver

2015-12-02 Thread Ingo Molnar
* Martin K. Petersen wrote: > > "Ingo" == Ingo Molnar 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 >

Re: MPT2SAS boot fail... due to silently loosing the driver

2015-12-02 Thread Ingo Molnar
* Martin K. Petersen wrote: > > "Ingo" == Ingo Molnar 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

Re: MPT2SAS boot fail... due to silently loosing the driver

2015-12-01 Thread Sreekanth Reddy
On Mon, Nov 30, 2015 at 10:51 PM, Martin K. Petersen wrote: > > > "Ingo" == Ingo Molnar 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

Re: MPT2SAS boot fail... due to silently loosing the driver

2015-12-01 Thread Sreekanth Reddy
On Mon, Nov 30, 2015 at 10:51 PM, Martin K. Petersen wrote: > > > "Ingo" == Ingo Molnar 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 >

Re: MPT2SAS boot fail... due to silently loosing the driver

2015-11-30 Thread James Bottomley
[cc to linux-scsi added] On Mon, 2015-11-30 at 12:21 -0500, Martin K. Petersen wrote: > > "Ingo" == Ingo Molnar 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

Re: MPT2SAS boot fail... due to silently loosing the driver

2015-11-30 Thread Christoph Hellwig
If that's been tested to work I'm fine with it. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: MPT2SAS boot fail... due to silently loosing the driver

2015-11-30 Thread Martin K. Petersen
> "Ingo" == Ingo Molnar 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 +

Re: MPT2SAS boot fail... due to silently loosing the driver

2015-11-30 Thread James Bottomley
[cc to linux-scsi added] On Mon, 2015-11-30 at 12:21 -0500, Martin K. Petersen wrote: > > "Ingo" == Ingo Molnar 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>

Re: MPT2SAS boot fail... due to silently loosing the driver

2015-11-30 Thread Christoph Hellwig
If that's been tested to work I'm fine with it. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: MPT2SAS boot fail... due to silently loosing the driver

2015-11-30 Thread Martin K. Petersen
> "Ingo" == Ingo Molnar 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

Re: MPT2SAS boot fail... due to silently loosing the driver

2015-11-26 Thread Ingo Molnar
* Martin K. Petersen wrote: > I guess we could do something like the following and let it sit for a > release cycle to help people transition. Bit of a hack, but it worked > for me in my quick testing... So I'm not sure how this could have worked for you in testing: try to set the MPT2SAS

Re: MPT2SAS boot fail... due to silently loosing the driver

2015-11-26 Thread Ingo Molnar
* Martin K. Petersen wrote: > > "Peter" == Peter Zijlstra writes: > > Peter> Please either create a fake MPT2SAS config that selects the > Peter> MPT3SAS driver, or rename the whole thing to MPT23SAS such that > Peter> we at least get a relevant question on oldconfig. > > Sorry about

Re: MPT2SAS boot fail... due to silently loosing the driver

2015-11-26 Thread Ingo Molnar
* Martin K. Petersen wrote: > > "Peter" == Peter Zijlstra writes: > > Peter> Please either create a fake MPT2SAS config that selects the > Peter> MPT3SAS driver, or rename the whole thing to MPT23SAS such that > Peter> we at least get a

Re: MPT2SAS boot fail... due to silently loosing the driver

2015-11-26 Thread Ingo Molnar
* Martin K. Petersen wrote: > I guess we could do something like the following and let it sit for a > release cycle to help people transition. Bit of a hack, but it worked > for me in my quick testing... So I'm not sure how this could have worked for you in testing:

Re: MPT2SAS boot fail... due to silently loosing the driver

2015-11-24 Thread Martin K. Petersen
> "Peter" == Peter Zijlstra writes: Peter> Please either create a fake MPT2SAS config that selects the Peter> MPT3SAS driver, or rename the whole thing to MPT23SAS such that Peter> we at least get a relevant question on oldconfig. Sorry about that, Peter. I get bitten by oldconfig all the

Re: MPT2SAS boot fail... due to silently loosing the driver

2015-11-24 Thread Ingo Molnar
* Christoph Hellwig wrote: > I wonder what the "classic" way to such transitions is. Adding a mpt2 option > that just selects mpt3 sound easy, but might be very confusing. I was hit by the same problem, and wasted some time on it before Peter did his time wasting, so a solution would be

Re: MPT2SAS boot fail... due to silently loosing the driver

2015-11-24 Thread Ingo Molnar
* Christoph Hellwig wrote: > I wonder what the "classic" way to such transitions is. Adding a mpt2 option > that just selects mpt3 sound easy, but might be very confusing. I was hit by the same problem, and wasted some time on it before Peter did his time wasting, so a solution

Re: MPT2SAS boot fail... due to silently loosing the driver

2015-11-24 Thread Martin K. Petersen
> "Peter" == Peter Zijlstra writes: Peter> Please either create a fake MPT2SAS config that selects the Peter> MPT3SAS driver, or rename the whole thing to MPT23SAS such that Peter> we at least get a relevant question on oldconfig. Sorry about that, Peter. I get bitten

Re: MPT2SAS boot fail... due to silently loosing the driver

2015-11-23 Thread Christoph Hellwig
Send a patch so we can understand what you mean :) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: MPT2SAS boot fail... due to silently loosing the driver

2015-11-23 Thread Hannes Reinecke
On 11/24/2015 08:51 AM, Christoph Hellwig wrote: > I wonder what the "classic" way to such transitions is. Adding a mpt2 > option that just selects mpt3 sound easy, but might be very confusing. > Personally, I would rename everything to 'mptXsas', and have the original options map onto that.

Re: MPT2SAS boot fail... due to silently loosing the driver

2015-11-23 Thread Christoph Hellwig
I wonder what the "classic" way to such transitions is. Adding a mpt2 option that just selects mpt3 sound easy, but might be very confusing. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at

MPT2SAS boot fail... due to silently loosing the driver

2015-11-23 Thread Peter Zijlstra
Hi all, Due to merging the MPT[23]SAS drivers (which undoubtedly is a good thing) my .config automagically lost its MPT2SAS entries and didn't ask for MPT3SAS because that was a pre-existing config which I didn't have selected. c84b06a48c4d ("mpt3sas: Single driver module which supports both

MPT2SAS boot fail... due to silently loosing the driver

2015-11-23 Thread Peter Zijlstra
Hi all, Due to merging the MPT[23]SAS drivers (which undoubtedly is a good thing) my .config automagically lost its MPT2SAS entries and didn't ask for MPT3SAS because that was a pre-existing config which I didn't have selected. c84b06a48c4d ("mpt3sas: Single driver module which supports both

Re: MPT2SAS boot fail... due to silently loosing the driver

2015-11-23 Thread Christoph Hellwig
I wonder what the "classic" way to such transitions is. Adding a mpt2 option that just selects mpt3 sound easy, but might be very confusing. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at

Re: MPT2SAS boot fail... due to silently loosing the driver

2015-11-23 Thread Hannes Reinecke
On 11/24/2015 08:51 AM, Christoph Hellwig wrote: > I wonder what the "classic" way to such transitions is. Adding a mpt2 > option that just selects mpt3 sound easy, but might be very confusing. > Personally, I would rename everything to 'mptXsas', and have the original options map onto that.

Re: MPT2SAS boot fail... due to silently loosing the driver

2015-11-23 Thread Christoph Hellwig
Send a patch so we can understand what you mean :) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/