From: Conor Dooley <conor.dooley@microchip.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Linux Crypto List <linux-crypto@vger.kernel.org>,
Jenny Zhang <jenny.zhang@starfivetech.com>,
Jia Jie Ho <jiajie.ho@starfivetech.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Walker Chen <walker.chen@starfivetech.com>
Subject: Re: linux-next: manual merge of the crypto tree with the riscv-soc tree
Date: Mon, 30 Jan 2023 07:54:17 +0000 [thread overview]
Message-ID: <Y9d3qWZYlULl8Vxq@wendy> (raw)
In-Reply-To: <20230130114128.692c7961@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
On Mon, Jan 30, 2023 at 11:41:28AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the crypto tree got a conflict in:
>
> MAINTAINERS
>
> between commit:
>
> 08b9a94e8654 ("soc: starfive: Add StarFive JH71XX pmu driver")
>
> from the riscv-soc tree and commit:
>
> c388f458bc34 ("hwrng: starfive - Add TRNG driver for StarFive SoC")
>
> from the crypto tree.
> Note, please keep MAINTAINERS file entries in alphabetical order.
Huh, good point. I didn't notice the PMU entry was added out of order.
> 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.
Thanks Stephen
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-01-30 7:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 0:41 linux-next: manual merge of the crypto tree with the riscv-soc tree Stephen Rothwell
2023-01-30 7:54 ` Conor Dooley [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y9d3qWZYlULl8Vxq@wendy \
--to=conor.dooley@microchip.com \
--cc=herbert@gondor.apana.org.au \
--cc=jenny.zhang@starfivetech.com \
--cc=jiajie.ho@starfivetech.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=walker.chen@starfivetech.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox