This patch marks the function mptsas_refreshing_device_handles(),
mptsas_expander_add() and mptsas_shutdown() as static in fusion/mptsas.c
because they are not used outside this file.
Thus, it also eliminates the following warnings in fusion/mptsas.c:
drivers/message/fusion/mptsas.c:1579:1: warnin
This patch marks the function mptscsih_quiesce_raid() as static in
fusion/mptspi.c because it is not used outside this function.
Thus, it also eliminates the following warning in fusion/mptspi.c:
drivers/message/fusion/mptspi.c:624:1: warning: no previous prototype for
‘mptscsih_quiesce_raid’ [-W
This patch marks the function mpt_SoftResetHandler() as static in mptbase.c
because it is not used outside this file.
Thus, it also eliminates the following warning in fusion/mptbase.c:
drivers/message/fusion/mptbase.c:7011:1: warning: no previous prototype for
‘mpt_SoftResetHandler’ [-Wmissing-p
Peter Chang wrote:
> 2013/12/12 Wakko Warner :
> > Kernel: vanilla 3.7.2.
> >
> > I have 2 mpt2sas controllers. I'm running a md check on the 2 arrays that I
> > have (one per card). I'm seeing this in my kernel log (last 4 lines):
> > 2013-12-10 19:52:10 kame kernel:[1558186.193904] mpt2sas0:
>
HI,
>> >> +- reg : First PHY memory resource is the SDS PHY access
>> >> + resource.
>> >> + Second PHY memory resoruce is the clock and
>> >> reset
>> >> + resources.
>> >> + Third PH
Hi,
On Thu, Dec 12, 2013 at 12:29 PM, Arnd Bergmann wrote:
> On Thursday 12 December 2013, Douglas Gilbert wrote:
>> >
>> >> +- apm,tx-speed : Tx operating speed. One set of 3-tuple for
>> >> + Gen1 (0x1), Gen2 (0x3), and Gen3 (0x7). Default is
>> >> +
On Wed, 11 Dec 2013, Sarah Sharp wrote:
> Hi Hans,
>
> I've been testing the UAS code you sent a pull request for against
> 3.13-rc1, and I've run into a rather nasty issue with USB disconnect.
>
> I ran some tests with a USB 3.0 storage device under xHCI. The disk has
> three 10GB partitions:
On Thursday 12 December 2013, Loc Ho wrote:
> Hi,
>
> > On Thursday 12 December 2013, Loc Ho wrote:
> >> +- reg : First PHY memory resource is the SDS PHY access
> >> + resource.
> >> + Second PHY memory resoruce is the clock and res
On Thursday 12 December 2013, James Bottomley wrote:
> > > I'm completely confused by this description. Can you rephrase this?
> > > It sounds like the only possible values are <1 3 7> for this property.
> >
> > Most likely Gen1, Gen2 and Gen3 are SATA-speak corresponding to SAS's
> > G1, G2 and G
On Thursday 12 December 2013, Douglas Gilbert wrote:
> >
> >> +- apm,tx-speed : Tx operating speed. One set of 3-tuple for
> >> + Gen1 (0x1), Gen2 (0x3), and Gen3 (0x7). Default is
> >> + 0x7.
> >
> > I'm completely confused by this description
Sie benötigen die Finanzierung? Wir bieten direkte Finanzierung zu
erschwinglichen Preisen. Unsere zuverlässige und bequeme Finanzierung
Dienstleistungen umfassen: - Konventionelle und Personal Finanzierung für
Einzelpersonen; Handelsregister Darlehen für mittlere und große Unternehmen
Ventur
2013/12/12 Wakko Warner :
> Kernel: vanilla 3.7.2.
>
> I have 2 mpt2sas controllers. I'm running a md check on the 2 arrays that I
> have (one per card). I'm seeing this in my kernel log (last 4 lines):
> 2013-12-10 19:52:10 kame kernel:[1558186.193904] mpt2sas0:
> log_info(0x3108): originat
Kernel: vanilla 3.7.2.
I have 2 mpt2sas controllers. I'm running a md check on the 2 arrays that I
have (one per card). I'm seeing this in my kernel log (last 4 lines):
2013-12-10 19:52:10 kame kernel:[1558186.193904] mpt2sas0:
log_info(0x3108): originator(PL), code(0x08), sub_code(0x)
On Thu, 2013-12-12 at 15:31 +0100, Douglas Gilbert wrote:
> On 13-12-12 02:27 PM, Arnd Bergmann wrote:
> > On Thursday 12 December 2013, Loc Ho wrote:
> >> +- reg : First PHY memory resource is the SDS PHY access
> >> + resource.
> >> +
Hi,
> On Thursday 12 December 2013, Loc Ho wrote:
>> +- reg : First PHY memory resource is the SDS PHY access
>> + resource.
>> + Second PHY memory resoruce is the clock and reset
>> + resources.
>> +
On 13-12-12 02:27 PM, Arnd Bergmann wrote:
On Thursday 12 December 2013, Loc Ho wrote:
+- reg : First PHY memory resource is the SDS PHY access
+ resource.
+ Second PHY memory resoruce is the clock and reset
+
On Thursday 12 December 2013, Loc Ho wrote:
> +- reg : First PHY memory resource is the SDS PHY access
> + resource.
> + Second PHY memory resoruce is the clock and reset
> + resources.
> +
Hi,
On 12/12/2013 01:07 AM, Sarah Sharp wrote:
Hi Hans,
I've been testing the UAS code you sent a pull request for against
3.13-rc1, and I've run into a rather nasty issue with USB disconnect.
I ran some tests with a USB 3.0 storage device under xHCI. The disk has
three 10GB partitions: ext3
When the host template doesn't declare an eh_host_reset_handler
the eh_deadline mechanism is pointless and will set the
device to offline. So disable eh_deadline if no
eh_host_reset_handler is present.
Cc: Ewan Milne
Signed-off-by: Hannes Reinecke
---
drivers/scsi/hosts.c | 2 +-
drivers/s
On 12/12/2013 08:54 AM, Nicholas A. Bellinger wrote:
> On Thu, 2013-12-12 at 08:18 +0100, Hannes Reinecke wrote:
[ .. ]
>> The problem here is that 'kthread_stop()' is supposed to be called
>> with a _valid_ task structure.
>>
>> There is this race window:
>>
>> np->np_thread_state = ISCSI_NP_
On Thu, 2013-12-12 at 08:18 +0100, Hannes Reinecke wrote:
> On 12/12/2013 12:44 AM, Nicholas A. Bellinger wrote:
> > I'm not sure this extra logic is necessary. How about just clearing
> > np->np_thread in iscsit_del_np instead..?
> >
> > Care to verify on your side with the following patch..?
21 matches
Mail list logo
