linux-kernel - linux-next: manual merge of the iio tree with the origin tree

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]

Message-Id: <20220221211943.2092199-1-broonie@kernel.org>
Date:   Mon, 21 Feb 2022 21:19:43 +0000
From:   broonie@...nel.org
To:     Jonathan Cameron <Jonathan.Cameron@...wei.com>
Cc:     Cai Huoqing <caihuoqing@...du.com>,
        Cai Huoqing <cai.huoqing@...ux.dev>,
        Jonathan Cameron <Jonathan.Cameron@...wei.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Marc Kleine-Budde <mkl@...gutronix.de>
Subject: linux-next: manual merge of the iio tree with the origin tree

Hi all,

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

  .mailmap

between commit:

  984d1efff2304 ("mailmap: update email address of Brian Silverman")

from the origin tree and commit:

  f3366f8e64645 ("mailmap: Update email address for Cai Huoqing")

from the iio 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.

diff --cc .mailmap
index 8cd44b0c65797,76dd303c7eac1..0000000000000
--- a/.mailmap
+++ b/.mailmap
@@@ -70,7 -70,7 +70,8 @@@ Boris Brezillon <bbrezillon@...nel.org
  Boris Brezillon <bbrezillon@...nel.org> <boris.brezillon@...e-electrons.com>
  Brian Avery <b.avery@...com>
  Brian King <brking@...ibm.com>
 +Brian Silverman <bsilver16384@...il.com> <brian.silverman@...erivertech.com>
+ Cai Huoqing <cai.huoqing@...ux.dev> <caihuoqing@...du.com>
  Changbin Du <changbin.du@...el.com> <changbin.du@...il.com>
  Changbin Du <changbin.du@...el.com> <changbin.du@...el.com>
  Chao Yu <chao@...nel.org> <chao2.yu@...sung.com>