On Tue, 2015-06-23 at 12:59 -0500, Timothy Pearson wrote:
> On 06/23/2015 12:56 PM, James Bottomley wrote:
> > On Tue, 2015-06-23 at 12:47 -0500, Timothy Pearson wrote:
> >> On 06/23/2015 12:45 PM, James Bottomley wrote:
> >>> On Tue, 2015-06-23 at 12:33 -0500, Timothy Pearson wrote:
> On 06/2
On 06/23/2015 12:56 PM, James Bottomley wrote:
On Tue, 2015-06-23 at 12:47 -0500, Timothy Pearson wrote:
On 06/23/2015 12:45 PM, James Bottomley wrote:
On Tue, 2015-06-23 at 12:33 -0500, Timothy Pearson wrote:
On 06/23/2015 08:35 AM, James Bottomley wrote:
On Tue, 2015-06-23 at 18:06 +0530, S
On Tue, 2015-06-23 at 12:47 -0500, Timothy Pearson wrote:
> On 06/23/2015 12:45 PM, James Bottomley wrote:
> > On Tue, 2015-06-23 at 12:33 -0500, Timothy Pearson wrote:
> >> On 06/23/2015 08:35 AM, James Bottomley wrote:
> >>> On Tue, 2015-06-23 at 18:06 +0530, Sreekanth Reddy wrote:
> Hi,
> >
On 06/23/2015 12:45 PM, James Bottomley wrote:
On Tue, 2015-06-23 at 12:33 -0500, Timothy Pearson wrote:
On 06/23/2015 08:35 AM, James Bottomley wrote:
On Tue, 2015-06-23 at 18:06 +0530, Sreekanth Reddy wrote:
Hi,
Upstream contributor should not add copyright to this driver code.
I can't ag
On Tue, 2015-06-23 at 12:33 -0500, Timothy Pearson wrote:
> On 06/23/2015 08:35 AM, James Bottomley wrote:
> > On Tue, 2015-06-23 at 18:06 +0530, Sreekanth Reddy wrote:
> >> Hi,
> >>
> >> Upstream contributor should not add copyright to this driver code.
> >
> > I can't agree with that as a general
On 06/23/2015 08:35 AM, James Bottomley wrote:
On Tue, 2015-06-23 at 18:06 +0530, Sreekanth Reddy wrote:
Hi,
Upstream contributor should not add copyright to this driver code.
I can't agree with that as a general rule: it depends on the
significance of the contribution. The somewhat ill defi
On Tue, Jun 23, 2015 at 7:05 PM, James Bottomley
wrote:
> On Tue, 2015-06-23 at 18:06 +0530, Sreekanth Reddy wrote:
>> Hi,
>>
>> Upstream contributor should not add copyright to this driver code.
>
> I can't agree with that as a general rule: it depends on the
> significance of the contribution.
On Tue, 2015-06-23 at 18:06 +0530, Sreekanth Reddy wrote:
> Hi,
>
> Upstream contributor should not add copyright to this driver code.
I can't agree with that as a general rule: it depends on the
significance of the contribution. The somewhat ill defined standard for
this is the contribution mus
Hi,
Upstream contributor should not add copyright to this driver code.
Regards,
Sreekanth
On Tue, Jun 23, 2015 at 9:24 AM, Joe Lawrence wrote:
>
>
> On 06/21/2015 02:46 PM, Timothy Pearson wrote:
>> On 06/16/2015 01:49 PM, Timothy Pearson wrote:
>>> On 06/16/2015 12:42 PM, Joe Lawrence wrote:
>
On 06/21/2015 02:46 PM, Timothy Pearson wrote:
> On 06/16/2015 01:49 PM, Timothy Pearson wrote:
>> On 06/16/2015 12:42 PM, Joe Lawrence wrote:
>>> On 06/16/2015 12:28 PM, Timothy Pearson wrote:
On 06/12/2015 05:05 PM, Timothy Pearson wrote:
> The mpt2sas driver crashes if the BIOS does n
On 06/16/2015 01:49 PM, Timothy Pearson wrote:
On 06/16/2015 12:42 PM, Joe Lawrence wrote:
On 06/16/2015 12:28 PM, Timothy Pearson wrote:
On 06/12/2015 05:05 PM, Timothy Pearson wrote:
The mpt2sas driver crashes if the BIOS does not set up at least one
memory I/O resource. This failure can hap
On 06/16/2015 12:42 PM, Joe Lawrence wrote:
On 06/16/2015 12:28 PM, Timothy Pearson wrote:
On 06/12/2015 05:05 PM, Timothy Pearson wrote:
The mpt2sas driver crashes if the BIOS does not set up at least one
memory I/O resource. This failure can happen if the device is too
slow to respond during
On 06/16/2015 12:28 PM, Timothy Pearson wrote:
> On 06/12/2015 05:05 PM, Timothy Pearson wrote:
>> The mpt2sas driver crashes if the BIOS does not set up at least one
>> memory I/O resource. This failure can happen if the device is too
>> slow to respond during POST and is missed by the BIOS, but L
On 06/12/2015 05:05 PM, Timothy Pearson wrote:
The mpt2sas driver crashes if the BIOS does not set up at least one
memory I/O resource. This failure can happen if the device is too
slow to respond during POST and is missed by the BIOS, but Linux
then detects the device later in the boot process.
The mpt2sas driver crashes if the BIOS does not set up at least one
memory I/O resource. This failure can happen if the device is too
slow to respond during POST and is missed by the BIOS, but Linux
then detects the device later in the boot process.
This patch aborts initialization and prints a
15 matches
Mail list logo