Hello!

Hello! MY Name Is Mrs Raymond.Mabel ,I am contacting you to help me And My Daughter to relocate to your country My husband was a serving director of the Gold exporting board until his death He Was planed and poisoned By his Family Members He made a deposit of ($6,500,000.00) here in

Re: [PATCH 1/2] qedi: Remove WARN_ON for untracked cleanup.

On 06/15/2017 12:10 AM, Manish Rangankar wrote: > Signed-off-by: Manish Rangankar > --- > drivers/scsi/qedi/qedi_fw.c | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/drivers/scsi/qedi/qedi_fw.c b/drivers/scsi/qedi/qedi_fw.c > index 8bc7ee1..507512c 100644 >

Re: [PATCH 2/2] qedi: Remove WARN_ON from clear task context.

On 06/15/2017 12:10 AM, Manish Rangankar wrote: > Signed-off-by: Manish Rangankar > --- > drivers/scsi/qedi/qedi_main.c | 4 +--- > 1 file changed, 1 insertion(+), 3 deletions(-) > > diff --git a/drivers/scsi/qedi/qedi_main.c b/drivers/scsi/qedi/qedi_main.c > index

[PATCH 3/6] qla2xxx: Add FC-NVMe F/W initialization and transport registration

From: Duane Grigsby This code provides the interfaces to register remote and local ports of FC4 type 0x28 with the FC-NVMe transport and transports the requests (FC-NVMe FC link services and FC-NVMe commands IUs) to the fabric. It also provides the support for

[PATCH 4/6] qla2xxx: Send FC4 type NVMe to the management server

From: Duane Grigsby This patch adds switch command support for FC-4 type of FC-NVMe (0x28) for resgistering HBA port to the management server. RFT_ID command is used to register FC-4 type of 0x28 and RFF_ID is used to register FC-4 features bits for FC-NVMe port.

[PATCH 1/6] qla2xxx: Add FC-NVMe port discovery and PRLI handling

From: Duane Grigsby Signed-off-by: Darren Trapp Signed-off-by: Duane Grigsby Signed-off-by: Anil Gurumurthy Signed-off-by: Giridhar Malavali Signed-off-by:

[PATCH 2/6] qla2xxx: Add FC-NVMe command handling

From: Duane Grigsby Signed-off-by: Darren Trapp Signed-off-by: Duane Grigsby Signed-off-by: Anil Gurumurthy Signed-off-by: Giridhar Malavali Signed-off-by:

[PATCH 0/6] qla2xxx: Add NVMe FC Fabric support in driver

Hi Martin, This patch series adds NVMe FC fabric support for qla2xxx initiator mode driver. This series depends on the target multiqueue series that was sent out on June 13,207. (https://www.spinics.net/lists/linux-scsi/msg109827.html) There are couple of new files qla_nvme.c and qla_nvme.h

[PATCH 5/6] qla2xxx: Use FC-NMVe FC4 type for FDMI registration

From: Duane Grigsby Signed-off-by: Duane Grigsby Signed-off-by: Darren Trapp Signed-off-by: Anil Gurumurthy Signed-off-by: Giridhar Malavali Signed-off-by:

[PATCH 6/6] qla2xxx: Update Driver version to 10.00.00.00-k

Signed-off-by: Himanshu Madhani --- drivers/scsi/qla2xxx/qla_version.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/scsi/qla2xxx/qla_version.h b/drivers/scsi/qla2xxx/qla_version.h index dcbb9bb05e99..005a378f7fab 100644 ---

Re: [PATCH v2 2/5] dt-bindings: scsi: ufs: add document for hi3660-ufs

On Fri, Jun 16, 2017 at 8:51 AM, Bu Tao wrote: > add ufs node document for hi3660 > > Signed-off-by: Bu Tao > --- > .../devicetree/bindings/ufs/hi3660-ufs.txt | 58 > ++ > 1 file changed, 58 insertions(+) > create mode

mptsas crash on expander hot-remove

I've got a disk box with a SAS expander connected to a card based on the LSI SAS1068E chip. I recently upgraded the machine from 4.5.7 to 4.11.5, and now disconnecting (i.e. hot removing) the SAS expander from the HBA results in fireworks like this: [ 4738.044119] end_device-6:0:0: mptsas:

[PATCH 03/11] au1100fb: remove a bogus dma_free_nonconsistent call

au1100fb is using managed dma allocations, so it doesn't need to explicitly free the dma memory in the error path (and if it did it would have to use the managed version). Signed-off-by: Christoph Hellwig --- drivers/video/fbdev/au1100fb.c | 4 1 file changed, 4 deletions(-)

Re: [PATCH 10/11] Driver responds LS_RJT to Beacon Off ELS - Linux

On 06/16/2017 07:56 AM, James Smart wrote: > Beacon OFF from switch is rejected by driver. > > Driver fails Beacon OFF if frequency is set to 0. As per fc-ls > spec, status, capability, frequency and duration fields are only > applicable for Beacon ON. > > Remove frequency and type checks.

Re: [PATCH 11/11] lpfc: update to revision to 11.4.0.1

On 06/16/2017 07:56 AM, James Smart wrote: > Set lpfc driver revision to 11.4.0.1 > > Signed-off-by: Dick Kennedy > Signed-off-by: James Smart > --- > drivers/scsi/lpfc/lpfc_version.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) >

Re: [alsa-devel] [PATCH 04/11] sound/hal2: switch to dma_alloc_attrs

On Fri, Jun 16, 2017 at 10:49:56AM +0200, Takashi Iwai wrote: > On Fri, 16 Jun 2017 09:17:09 +0200, > Christoph Hellwig wrote: > > > > Use dma_alloc_attrs directly instead of the dma_alloc_noncoherent wrapper. > > > > Signed-off-by: Christoph Hellwig > > Should I take this one

[PATCH 01/11] dma-mapping: remove dmam_free_noncoherent

This function was never used since it was added. Signed-off-by: Christoph Hellwig --- Documentation/driver-model/devres.txt | 1 - drivers/base/dma-mapping.c| 20 include/linux/dma-mapping.h | 2 -- 3 files changed, 23 deletions(-) diff

[PATCH 04/11] sound/hal2: switch to dma_alloc_attrs

Use dma_alloc_attrs directly instead of the dma_alloc_noncoherent wrapper. Signed-off-by: Christoph Hellwig --- sound/mips/hal2.c | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/sound/mips/hal2.c b/sound/mips/hal2.c index

[PATCH 02/11] dma-mapping: replace dmam_alloc_noncoherent with dmam_alloc_attrs

dmam_alloc_noncoherent is a trivial wrapper around dmam_alloc_attrs, that hardcodes one particular flag. Make the devres code more flexible by allowing the callers to pass arbitrary flags. Signed-off-by: Christoph Hellwig --- Documentation/driver-model/devres.txt | 2 +-

Re: [PATCH 03/11] Vport creation is failing with "Link Down" error

On 06/16/2017 07:56 AM, James Smart wrote: > Vport creation fails for SLI-3 adapters. > > Mailbox submission fails because mailbox interrupt is disabled. Mailbox > interrupt is disabled during port reset. > > Do reset only for physical port. > > Signed-off-by: Dick Kennedy

Re: [PATCH 04/11] Reduce time spent in IRQ for received NVME commands

On 06/16/2017 07:56 AM, James Smart wrote: > Removed unnecessary bzero of context area. Due to size of sg list, > added a substantial delay and played havoc on cpu caches. > > Signed-off-by: Dick Kennedy > Signed-off-by: James Smart > --- >

[PATCH] scsi: default to scsi-mq

Remove the SCSI_MQ_DEFAULT config option and default to the blk-mq I/O path now that we had plenty of testing, and have I/O schedulers for blk-mq. The module option to disable the blk-mq path is kept around for now. Signed-off-by: Christoph Hellwig --- drivers/scsi/Kconfig | 11

Re: [alsa-devel] [PATCH 04/11] sound/hal2: switch to dma_alloc_attrs

On Fri, 16 Jun 2017 10:51:47 +0200, Christoph Hellwig wrote: > > On Fri, Jun 16, 2017 at 10:49:56AM +0200, Takashi Iwai wrote: > > On Fri, 16 Jun 2017 09:17:09 +0200, > > Christoph Hellwig wrote: > > > > > > Use dma_alloc_attrs directly instead of the dma_alloc_noncoherent wrapper. > > > > > >

Re: [PATCH 09/11] Fix crash in lpfc_sli_ringtxcmpl_put when nvmet gets an abort request.

On 06/16/2017 07:56 AM, James Smart wrote: > When running nvme detach-ns /dev/nvme0n1 -n 1 command, > the nvmet lpfc driver crashes with this stack dump: > > kernel BUG at /root/NVME/lpfc_8.4/lpfc_sli.c:1393! > invalid opcode: [#1] SMP > Workqueue: nvmet-fc-cpu0 nvmet_fc_do_work_on_cpu

Re: [PATCH 08/11] Fix crash doing IO with resets

On 06/16/2017 07:56 AM, James Smart wrote: > During every reset, IOCBs are allocated. So, at one point, number of > allocated IOCBs reaches maximum limit and lpfc_sli_next_iotag fails. > > Allocate IOCBs only during initialization. Reuse them after every reset > instead of allocating new set of

Re: [alsa-devel] [PATCH 04/11] sound/hal2: switch to dma_alloc_attrs

On Fri, 16 Jun 2017 09:17:09 +0200, Christoph Hellwig wrote: > > Use dma_alloc_attrs directly instead of the dma_alloc_noncoherent wrapper. > > Signed-off-by: Christoph Hellwig Should I take this one through sound git tree, or would you prefer taking all through another? In the

Re: [PATCH 06/11] Fix SLI3 drivers attempting NVME ELS commands.

On 06/16/2017 07:56 AM, James Smart wrote: > In a server with an 8G adapter and a 32G adapter, running NVME > and FCP, the server would crash with the following stack. > > RIP: 0010: ... lpfc_nvme_register_port+0x38/0x420 [lpfc] > lpfc_nlp_state_cleanup+0x154/0x4f0 [lpfc] >

Re: [PATCH 07/11] Fix crash after firmware flash when IO is running.

On 06/16/2017 07:56 AM, James Smart wrote: > OS crashes after the completion of firmware download. > > Failure in posting SCSI SGL buffers because number of SGL buffers > is less than total count. Some of the pending IOs are not completed > by driver. SGL buffers for these IOs are not added back

Re: [PATCH 02/11] Fix nvme_info sysfs output to be consistent

On 06/16/2017 07:56 AM, James Smart wrote: > First line of nvme_info output is not consistent > > There is an Extra colon in the format. > > First line of output will contain one of the following strings: > NVME Initiator Enabled > NVME Target Enabled > NVME Disabled > > Signed-off-by: Dick

Re: [PATCH 01/11] Fix system panic when express lane enabled.

On 06/16/2017 07:56 AM, James Smart wrote: > There is a null pointer dereference that can happen in the FOF interrupt > handler. > > The driver was not setting up cq->assoc_qp_for sli4_hba->oas_cq. > > Initialize cq->assoc_qp before accessing it. > > Signed-off-by: Dick Kennedy

Re: [PATCH 05/11] Break up IO ctx list into a separate get and put list

On 06/16/2017 07:56 AM, James Smart wrote: > Since unsol rcv ISR and command cmpl ISR both access/lock > this list, a separate get/put lists will reduce contention. > > Replaced > struct list_head lpfc_nvmet_ctx_list; > with > struct list_head lpfc_nvmet_ctx_get_list; > struct list_head

[PATCH v2 5/5] arm64: defconfig: enable f2fs and squashfs

Partitions in HiKey960 are formatted as f2fs and squashfs. f2fs is for userdata; squashfs is for system. Both partitions are required by Android. Signed-off-by: Zhangfei Gao Signed-off-by: Chen Jun Signed-off-by: Guodong Xu

[PATCH v2 3/5] arm64: dts: Add ufs dts node

arm64: dts: add ufs node for hi3660 Signed-off-by: Bu Tao --- arch/arm64/boot/dts/hisilicon/hi3660-hikey960.dts | 9 + arch/arm64/boot/dts/hisilicon/hi3660.dtsi | 19 +++ 2 files changed, 28 insertions(+) diff --git

[PATCH 11/11] dma-mapping: remove dma_alloc_noncoherent and dma_free_noncoherent

No users left, everyone switched to the _attrs versions. Signed-off-by: Christoph Hellwig --- Documentation/DMA-API.txt| 30 -- arch/metag/include/asm/dma-mapping.h | 2 +- arch/nios2/include/asm/dma-mapping.h | 2 +-

remove dma_alloc_noncoherent

For many years we've had the dma_alloc_attrs API that is more flexible than dma_alloc_noncoherent. This series moves the remaining users over to the attrs API.

[PATCH v2 0/5] scsi: ufs: add ufs driver code for Hi3660 SoC

This patchset adds driver support for UFS for Hi3660 SoC. It is verified on HiKey960 board In v2 The dts ufs node patch, v2-0003-arm64-dts-Add-ufs-dts-node-for-Hisilicon-Hi3660-S.patch, is dependent on the patch below: >From Guodong Xu

[PATCH v2 4/5] arm64: defconfig: enable configs for hi3660 ufs

This enable configs for Hi3660 UFS driver. Reviewed-by: Chen Feng Signed-off-by: Zhangfei Gao Signed-off-by: Chen Jun Signed-off-by: Guodong Xu --- arch/arm64/configs/defconfig | 3 +++ 1 file

[PATCH v2 2/5] dt-bindings: scsi: ufs: add document for hi3660-ufs

add ufs node document for hi3660 Signed-off-by: Bu Tao --- .../devicetree/bindings/ufs/hi3660-ufs.txt | 58 ++ 1 file changed, 58 insertions(+) create mode 100644 Documentation/devicetree/bindings/ufs/hi3660-ufs.txt diff --git

[PATCH v2 1/5] scsi: ufs: add hi3660 ufs driver code

add hi3660 ufs driver code Signed-off-by: Geng Jianfeng Signed-off-by: Bu Tao Signed-off-by: Zang Leigang Signed-off-by: Yu Jianfeng --- drivers/scsi/ufs/Kconfig | 8 +

Re: [ANNOUNCE]: Broadcom (Emulex) FC Target driver - efct

On 06/14/2017 10:02 PM, Sebastian Herbszt wrote: > Hannes Reinecke wrote: >> On 06/13/2017 01:08 AM, James Smart wrote: > > [snip] > >>> Questions: >>> a) How best to deal with overlapping pci id's ? E.g. if we do (1) >>> and we have an initiator and target driver, there is a lot of >>>

[PATCH 08/11] sgiseeq: switch to dma_alloc_attrs

Use dma_alloc_attrs directly instead of the dma_alloc_noncoherent wrapper. Signed-off-by: Christoph Hellwig --- drivers/net/ethernet/seeq/sgiseeq.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/net/ethernet/seeq/sgiseeq.c

[PATCH 07/11] 53c700: switch to dma_alloc_attrs

Use dma_alloc_attrs directly instead of the dma_alloc_noncoherent wrapper. Signed-off-by: Christoph Hellwig --- drivers/scsi/53c700.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/scsi/53c700.c b/drivers/scsi/53c700.c index

[PATCH 10/11] i825xx: switch to switch to dma_alloc_attrs

This way we can always pass DMA_ATTR_NON_CONSISTENT, the SNI mips version will simply ignore the flag. Signed-off-by: Christoph Hellwig --- drivers/net/ethernet/i825xx/lasi_82596.c | 6 ++ drivers/net/ethernet/i825xx/lib82596.c | 9 +

[PATCH 06/11] sigwd93: switch to dma_alloc_attrs

Use dma_alloc_attrs directly instead of the dma_alloc_noncoherent wrapper. Signed-off-by: Christoph Hellwig --- drivers/scsi/sgiwd93.c | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/drivers/scsi/sgiwd93.c b/drivers/scsi/sgiwd93.c index

[PATCH 05/11] serial/mpsc: switch to dma_alloc_attrs

Use dma_alloc_attrs directly instead of the dma_alloc_noncoherent wrapper. Signed-off-by: Christoph Hellwig --- drivers/tty/serial/mpsc.c | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/drivers/tty/serial/mpsc.c b/drivers/tty/serial/mpsc.c index

[PATCH 09/11] au1000_eth: switch to dma_alloc_attrs

Use dma_alloc_attrs directly instead of the dma_alloc_noncoherent wrapper. Signed-off-by: Christoph Hellwig --- drivers/net/ethernet/amd/au1000_eth.c | 18 ++ 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/drivers/net/ethernet/amd/au1000_eth.c

Re: [RFC] enclosure: fix sysfs symlinks creation when using multipath

Dne 16.6.2017 v 14:40 Douglas Miller napsal(a): > > I'd like to add that we are seeing this problem with singlepath installations > and need to get this fixed upstream as soon as possible. RHEL new product > contains this fix and is working for us, but we need to be able to offer > other

Re: [RFC] enclosure: fix sysfs symlinks creation when using multipath

On 02/07/2017 08:08 AM, Maurizio Lombardi wrote: With multipath, it may happen that the same device is passed to enclosure_add_device() multiple times and that the enclosure_add_links() function fails to create the symlinks because the device's sysfs directory entry is still NULL. In this case,

Re: [RFC] enclosure: fix sysfs symlinks creation when using multipath

On 06/16/2017 07:48 AM, Maurizio Lombardi wrote: Dne 16.6.2017 v 14:40 Douglas Miller napsal(a): I'd like to add that we are seeing this problem with singlepath installations and need to get this fixed upstream as soon as possible. RHEL new product contains this fix and is working for us,

Re: [PATCH] scsi_proto.h: ATA_32 added for ata pass-thru(32).

On Thu, 2017-06-15 at 20:29 +0900, Minwoo Im wrote: > SAT-4(SCSI/ATA Translation Standard) supports a ATA PASS-THROUGH(32) > SCSI command. It uses 7Fh as a operation code which means > variable-length CDB. > It would be great if kernel supports an ata pass-thru(32) command. > Prior to development

[RFC] ubsan: signed integer overflow in scsi_partsize

A Gentoo user reported a USBAN signed integer overflow in scsicam.c Shall we change something? kernel: UBSAN: Undefined behaviour in drivers/scsi/scsicam.c:173:29 kernel: signed integer overflow: kernel: 62015235 *

Re: enclosure: fix sysfs symlinks creation when using multipath

On 06/16/2017 10:41 AM, Douglas Miller wrote: On 03/16/2017 01:49 PM, James Bottomley wrote: On Wed, 2017-03-15 at 19:39 -0400, Martin K. Petersen wrote: Maurizio Lombardi writes: With multipath, it may happen that the same device is passed to enclosure_add_device()

Re: enclosure: fix sysfs symlinks creation when using multipath

On 03/16/2017 01:49 PM, James Bottomley wrote: On Wed, 2017-03-15 at 19:39 -0400, Martin K. Petersen wrote: Maurizio Lombardi writes: With multipath, it may happen that the same device is passed to enclosure_add_device() multiple times and that the enclosure_add_links()