On 05/14/2014 05:57 PM, Nicholas A. Bellinger wrote:
On Wed, 2014-05-14 at 17:22 -0700, Andy Grover wrote:
On 05/14/2014 05:07 PM, Nicholas A. Bellinger wrote:
On Wed, 2014-05-14 at 15:48 -0700, Andy Grover wrote:
Just like for pSCSI, if the transport sets get_write_cache, then it is
not valid
On Wed, 2014-05-14 at 17:22 -0700, Andy Grover wrote:
> On 05/14/2014 05:07 PM, Nicholas A. Bellinger wrote:
> > On Wed, 2014-05-14 at 15:48 -0700, Andy Grover wrote:
> >> Just like for pSCSI, if the transport sets get_write_cache, then it is
> >> not valid to enable write cache emulation for it. R
On 05/14/2014 05:07 PM, Nicholas A. Bellinger wrote:
On Wed, 2014-05-14 at 15:48 -0700, Andy Grover wrote:
Just like for pSCSI, if the transport sets get_write_cache, then it is
not valid to enable write cache emulation for it. Return an error.
see https://bugzilla.redhat.com/show_bug.cgi?id=10
On Wed, 2014-05-14 at 15:48 -0700, Andy Grover wrote:
> Just like for pSCSI, if the transport sets get_write_cache, then it is
> not valid to enable write cache emulation for it. Return an error.
>
> see https://bugzilla.redhat.com/show_bug.cgi?id=1082675
>
> Reviewed-by: Chris Leech
> Signed-of
Just like for pSCSI, if the transport sets get_write_cache, then it is
not valid to enable write cache emulation for it. Return an error.
see https://bugzilla.redhat.com/show_bug.cgi?id=1082675
Reviewed-by: Chris Leech
Signed-off-by: Andy Grover
---
drivers/target/target_core_device.c | 8
5 matches
Mail list logo