From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Helge Deller <deller@gmx.de>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Vlastimil Babka <vbabka@kernel.org>
Subject: Re: linux-next: manual merge of the fbdev tree with the mm tree
Date: Tue, 13 Oct 2026 17:50:20 +0100 [thread overview]
Message-ID: <as5hGf0IS-LccM0_@gremlin> (raw)
In-Reply-To: <as5bwyKpGQaBZ3CO@sirena.org.uk>
On Tue, Oct 13, 2026 at 05:26:43PM +0100, Mark Brown wrote:
> Hi all,
>
> Today's linux-next merge of the fbdev tree got a conflict in:
>
> drivers/video/fbdev/ssd1307fb.c
>
> between commit:
>
> d4488917e79c7 ("fbdev: defio: assert FBINFO_VIRTFB, drop VM_IO, add VM_MIXEDMAP")
>
> from the mm tree and commit:
>
> 81ae1f9a6c850 ("fbdev: ssd1307fb: check for fb_deferred_io_init() error")
Wow a conflict between two of my patches I have literally no excuses here :))
> diff --cc drivers/video/fbdev/ssd1307fb.c
> index db61d710fccb0,8fd96c37ee1ab..0000000000000
> --- a/drivers/video/fbdev/ssd1307fb.c
> +++ b/drivers/video/fbdev/ssd1307fb.c
> @@@ -767,9 -767,11 +767,13 @@@ static int ssd1307fb_probe(struct i2c_c
> info->fix.smem_start = __pa(vmem);
> info->fix.smem_len = vmem_size;
>
> + info->flags = FBINFO_VIRTFB;
> +
> - fb_deferred_io_init(info);
> + ret = fb_deferred_io_init(info);
> + if (ret) {
> + dev_err(dev, "failed to init fb deferred io: %d\n", ret);
> + goto fb_defio_error;
> + }
>
> i2c_set_clientdata(client, info);
>
LGTM thanks :)
--
Cheers, Lorenzo
prev parent reply other threads:[~2026-10-13 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 16:26 linux-next: manual merge of the fbdev tree with the mm tree Mark Brown
2026-10-13 16:50 ` Lorenzo Stoakes (ARM) [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=as5hGf0IS-LccM0_@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=david@kernel.org \
--cc=deller@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=vbabka@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.