On 5 July 2016 at 15:56, Joe Perches wrote:
> On Tue, 2016-07-05 at 15:36 -0700, Markus Mayer wrote:
>> On 5 July 2016 at 15:14, Joe Perches wrote:
>> > On Tue, 2016-07-05 at 13:47 -0700, Markus Mayer wrote:
>> > > This series introduces a family of generic
On Tue, 2016-07-05 at 15:36 -0700, Markus Mayer wrote:
> On 5 July 2016 at 15:14, Joe Perches wrote:
> > On Tue, 2016-07-05 at 13:47 -0700, Markus Mayer wrote:
> > > This series introduces a family of generic string case conversion
> > > functions. This kind of functionality is
On Wed, Jul 06, 2016 at 03:10:51AM +0800, Tom Yan wrote:
> Well it is exactly what the patch does. We no longer do the "divide it
> by 8" thing each time we want to know the now defined TRIM_RANGE_NUM.
>
> ata_set_lba_range_entries() has only been used by
> ata_scsi_write_same_xlat()
>
Hello,
On Wed, Jul 06, 2016 at 03:13:31AM +0800, Tom Yan wrote:
> I just thought that such a minor change in a comment can fit in the
> same patch where the issue was first noticed. Anyway, will split them
> if I am going to send a v3 set.
>
> On 5 July 2016 at 19:08, Sergei Shtylyov
>
On 5 July 2016 at 15:14, Joe Perches wrote:
> On Tue, 2016-07-05 at 13:47 -0700, Markus Mayer wrote:
>> This series introduces a family of generic string case conversion
>> functions. This kind of functionality is needed in several places in
>> the kernel. Right now, everybody
On Tue, 2016-07-05 at 13:47 -0700, Markus Mayer wrote:
> This series introduces a family of generic string case conversion
> functions. This kind of functionality is needed in several places in
> the kernel. Right now, everybody seems to be implementing their own
> copy of this functionality.
>
>
On Thu, May 26, 2016 at 9:58 PM, Varun Prakash wrote:
> Hi Or, Nicholas and Steve
> Thank you for the feedback and apologies for the delay in my response.
> On Wed, May 25, 2016 at 09:55:04PM -0700, Nicholas A. Bellinger wrote:
>> Varun + Co have made common improvements
I just got a HP Proliant DL360G6 with a PCI-E FC card from HP and got
this warning during driver initialization:
[4.166160] qla2xxx [:00:00.0]-0005: : QLogic Fibre Channel HBA Driver:
8.07.00.33-k.
[4.166633] qla2xxx [:07:00.0]-001d: : Found an ISP2432 irq 48 iobase
I tried UBSAN on one of my servers with QLogic FC adapter and got the
following UBSAN warning on x86-64:
[4.250370]
[4.250692] UBSAN: Undefined behaviour in
drivers/scsi/qla2xxx/qla_isr.c:2500:14
[
After introducing generic strtolower(), iscsi_initiatorname_tolower() is
no longer needed.
Signed-off-by: Markus Mayer
---
drivers/target/iscsi/iscsi_target_nego.c | 17 +
1 file changed, 1 insertion(+), 16 deletions(-)
diff --git
Add a collection of generic functions to convert strings to lowercase
or uppercase.
Changing the case of a string (with or without copying it first) seems
to be a recurring requirement in the kernel that is currently being
solved by several duplicated implementations doing the same thing. This
This series introduces a family of generic string case conversion
functions. This kind of functionality is needed in several places in
the kernel. Right now, everybody seems to be implementing their own
copy of this functionality.
Based on the discussion of the previous version of this series[1]
> "Linus" == Linus Torvalds writes:
Linus> It's not in my tree, at least.
Not in scsi-fixes either. I have been waiting for a "real" patch
submission with one or more Tested-by: tags. I generally don't queue
something that comes with a "try this untested
I just thought that such a minor change in a comment can fit in the
same patch where the issue was first noticed. Anyway, will split them
if I am going to send a v3 set.
On 5 July 2016 at 19:08, Sergei Shtylyov
wrote:
> On 7/5/2016 9:45 AM, tom.t...@gmail.com
Well it is exactly what the patch does. We no longer do the "divide it
by 8" thing each time we want to know the now defined TRIM_RANGE_NUM.
ata_set_lba_range_entries() has only been used by
ata_scsi_write_same_xlat()
(http://lxr.free-electrons.com/ident?i=ata_set_lba_range_entries,
although the
On 05.07.2016 19:32, Linus Torvalds wrote:
> On Tue, Jul 5, 2016 at 9:30 AM, Josh Boyer wrote:
>> On Wed, Jun 22, 2016 at 11:57 AM, Quinn Tran wrote:
>>>
>>> - if (rsp->msix->cpuid != smp_processor_id()) {
>>> + if (rsp->msix &&
On Tue, Jul 5, 2016 at 9:30 AM, Josh Boyer wrote:
> On Wed, Jun 22, 2016 at 11:57 AM, Quinn Tran wrote:
>>
>> - if (rsp->msix->cpuid != smp_processor_id()) {
>> + if (rsp->msix && (rsp->msix->cpuid != smp_processor_id())) {
>
> Did
This is not driven by the hotplug conversation but while I am at it
looks like a good candidate. Converting the thread to a kworker user
removes also the kthread member from struct fcoe_percpu_s.
This driver uses the struct fcoe_percpu_s but it does not need the
crc_eof_page member, only the work
The caller of bnx2fc_abts_cleanup() holds the tgt->tgt_lock lock and it
is expected to release the lock during wait_for_completion() and acquire
the lock afterwards.
This patch was only compile-tested due to -ENODEV.
Cc: qlogic-storage-upstr...@qlogic.com
Cc: Christoph Hellwig
The driver creates its own per-CPU threads which are updated based on CPU
hotplug events. It is also possible to use kworkers and remove some of the
infrastructure get the same job done while saving a few lines of code.
bnx2fc_percpu_io_thread() becomes bnx2fc_percpu_io_work() which is
mostly the
- All symbols which are only used within one .c file are marked static
and removed from the bnx2fc.h file if possible.
- the declarion of bnx2fc_percpu is moved into the header file
This patch was only compile-tested due to -ENODEV.
Cc: qlogic-storage-upstr...@qlogic.com
Cc: Christoph Hellwig
On Tue, Jun 28, 2016 at 01:28:19PM -0700, Tyrel Datwyler wrote:
> On 06/15/2016 06:00 AM, Johannes Thumshirn wrote:
> > Check for the existance of pciob->vport before accessing it.
>
> piocb mispelled.
Oops
>
> >
> > Signed-off-by: Johannes Thumshirn
> > ---
> >
On 7/5/2016 9:45 AM, tom.t...@gmail.com wrote:
From: Tom Yan
It does not make sense and is confusing to respond with "Invalid
field in CDB" while we have no support at all implemented for
FORMAT UNIT. It is decent to let it go to the default, which
will respond with
Hello.
On 7/5/2016 9:45 AM, tom.t...@gmail.com wrote:
From: Tom Yan
Define TRIM_RANGE_SIZE and TRIM_RANGE_NUM so that the corresponding
functions can be more generalized. Also, conform to SBC by rejecting
WRITE SAME (16) commands with number of blocks that exceeds the
From: Tom Yan
Define TRIM_RANGE_SIZE and TRIM_RANGE_NUM so that the corresponding
functions can be more generalized. Also, conform to SBC by rejecting
WRITE SAME (16) commands with number of blocks that exceeds the limit
that is defined in the SATL.
Signed-off-by: Tom Yan
From: Tom Yan
It does not make sense and is confusing to respond with "Invalid
field in CDB" while we have no support at all implemented for
FORMAT UNIT. It is decent to let it go to the default, which
will respond with "Invalid command operation code" instead.
26 matches
Mail list logo