linux-kernel - linux-next: manual merge of the scsi tree with the jc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:   Tue, 27 Jun 2017 14:29:31 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     James Bottomley <James.Bottomley@...senPartnership.com>,
        Jonathan Corbet <corbet@....net>
Cc:     Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Mauro Carvalho Chehab <mchehab@...pensource.com>,
        Tyrel Datwyler <tyreld@...ux.vnet.ibm.com>,
        "Martin K. Petersen" <martin.petersen@...cle.com>
Subject: linux-next: manual merge of the scsi tree with the jc_docs tree

Hi all,

Today's linux-next merge of the scsi tree got a conflict in:

  drivers/scsi/scsi_transport_fc.c

between commit:

  739aca06a2d2 ("scsi: fix some kernel-doc markups")

from the jc_docs tree and commit:

  134699d2a896 ("scsi: fix typos and grammar in comments of scsi_transport_fc.c")

from the scsi tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc drivers/scsi/scsi_transport_fc.c
index 1df77453f6b6,6dd0922a499d..000000000000
--- a/drivers/scsi/scsi_transport_fc.c
+++ b/drivers/scsi/scsi_transport_fc.c
@@@ -2914,18 -2914,16 +2914,18 @@@ EXPORT_SYMBOL(fc_remote_port_add)
   * port is no longer part of the topology. Note: Although a port
   * may no longer be part of the topology, it may persist in the remote
   * ports displayed by the fc_host. We do this under 2 conditions:
 + *
   * 1) If the port was a scsi target, we delay its deletion by "blocking" it.
 - *   This allows the port to temporarily disappear, then reappear without
 - *   disrupting the SCSI device tree attached to it. During the "blocked"
 - *   period the port will still exist.
 + *    This allows the port to temporarily disappear, then reappear without
 + *    disrupting the SCSI device tree attached to it. During the "blocked"
 + *    period the port will still exist.
 + *
   * 2) If the port was a scsi target and disappears for longer than we
 - *   expect, we'll delete the port and the tear down the SCSI device tree
 - *   attached to it. However, we want to semi-persist the target id assigned
 - *   to that port if it eventually does exist. The port structure will
 - *   remain (although with minimal information) so that the target id
 - *   bindings also remain.
 + *    expect, we'll delete the port and the tear down the SCSI device tree
 + *    attached to it. However, we want to semi-persist the target id assigned
 + *    to that port if it eventually does exist. The port structure will
 + *    remain (although with minimal information) so that the target id
-  *    bindings remails.
++ *    bindings also remain.
   *
   * If the remote port is not an FCP Target, it will be fully torn down
   * and deallocated, including the fc_remote_port class device.