From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Yury Norov <yury.norov@gmail.com>,
Hugo Villeneuve <hvilleneuve@dimonoff.com>,
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 bitmap tree with the tty tree
Date: Mon, 8 Jan 2024 08:53:40 +0100 [thread overview]
Message-ID: <2024010830-swimsuit-ferment-8b88@gregkh> (raw)
In-Reply-To: <20240108143627.29ac91fe@canb.auug.org.au>
On Mon, Jan 08, 2024 at 02:36:27PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the bitmap tree got a conflict in:
>
> drivers/tty/serial/sc16is7xx.c
>
> between commits:
>
> 8a1060ce9749 ("serial: sc16is7xx: fix invalid sc16is7xx_lines bitfield in case of probe error")
> 3837a0379533 ("serial: sc16is7xx: improve regmap debugfs by using one regmap per port")
>
> from the tty tree and commit:
>
> e63a961be48f ("serial: sc12is7xx: optimize sc16is7xx_alloc_line()")
>
> from the bitmap tree.
>
> I fixed it up (the former removed the function updated by the latter) 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.
Fix looks coks correct, thanks.
greg k-h
next prev parent reply other threads:[~2024-01-08 7:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 3:36 linux-next: manual merge of the bitmap tree with the tty tree Stephen Rothwell
2024-01-08 7:53 ` Greg KH [this message]
2024-01-08 16:51 ` Hugo Villeneuve
2024-01-11 14:39 ` Yury Norov
2024-01-17 8:14 ` Greg KH
2024-01-17 8:49 ` Stephen Rothwell
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=2024010830-swimsuit-ferment-8b88@gregkh \
--to=greg@kroah.com \
--cc=hvilleneuve@dimonoff.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=yury.norov@gmail.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