From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnd Bergmann <arnd@arndb.de>,
Akshay Gupta <akshay.gupta@amd.com>,
Jean Delvare <jdelvare@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the char-misc tree with the char-misc.current tree
Date: Fri, 24 Oct 2025 07:24:04 +0200 [thread overview]
Message-ID: <2025102457-sleek-unrented-a6f9@gregkh> (raw)
In-Reply-To: <20251024124906.70323e51@canb.auug.org.au>
On Fri, Oct 24, 2025 at 12:49:06PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the char-misc tree got a conflict in:
>
> drivers/misc/amd-sbi/Kconfig
>
> between commit:
>
> 70ad06df73a9 ("misc: amd-sbi: Clarify that this is a BMC driver")
>
> from the char-misc.current tree and commit:
>
> 5c7dddd7360b ("misc: amd-sbi: Add support for SB-RMI over I3C")
>
> from the char-misc 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/misc/amd-sbi/Kconfig
> index ab594908cb4a,acf0450ba220..000000000000
> --- a/drivers/misc/amd-sbi/Kconfig
> +++ b/drivers/misc/amd-sbi/Kconfig
> @@@ -2,11 -2,11 +2,13 @@@
> config AMD_SBRMI_I2C
> tristate "AMD side band RMI support"
> depends on I2C
> + depends on ARM || ARM64 || COMPILE_TEST
> select REGMAP_I2C
> + depends on I3C || !I3C
> + select REGMAP_I3C if I3C
> help
> - Side band RMI over I2C support for AMD out of band management.
> + Side band RMI over I2C/I3C support for AMD out of band management.
> + This driver is intended to run on the BMC, not the managed node.
>
> This driver can also be built as a module. If so, the module will
> be called sbrmi-i2c.
Looks good to me, thanks!
greg k-h
next prev parent reply other threads:[~2025-10-24 5:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 1:49 linux-next: manual merge of the char-misc tree with the char-misc.current tree Stephen Rothwell
2025-10-24 5:24 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-06 3:49 Stephen Rothwell
2021-12-06 13:43 ` Andy Shevchenko
2021-12-06 16:17 ` Ralph Siemsen
2021-12-06 16:44 ` Andy Shevchenko
2021-12-13 9:18 ` Greg KH
2022-01-07 23:18 ` Kees Cook
2019-10-18 3:26 Stephen Rothwell
2019-10-18 10:06 ` Greg KH
2019-04-03 3:56 Stephen Rothwell
2019-04-03 5:06 ` Srinivas Kandagatla
2019-04-03 6:39 ` Bo YU
2018-12-04 4:35 Stephen Rothwell
2018-12-04 7:42 ` Greg KH
2018-12-04 8:46 ` Dexuan Cui
2018-12-10 9:47 ` Greg KH
2018-12-10 18:51 ` Dexuan Cui
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=2025102457-sleek-unrented-a6f9@gregkh \
--to=greg@kroah.com \
--cc=akshay.gupta@amd.com \
--cc=arnd@arndb.de \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).