From: Javier Martinez Canillas <javierm@redhat.com>
To: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>,
Alex Deucher <alexander.deucher@amd.com>,
Guenter Roeck <linux@roeck-us.net>, Helge Deller <deller@gmx.de>,
Sam Ravnborg <sam@ravnborg.org>,
Xiyu Yang <xiyuyang19@fudan.edu.cn>,
Zhen Lei <thunder.leizhen@huawei.com>,
linux-fbdev@vger.kernel.org
Subject: Re: [RESEND RFC PATCH 4/5] fbdev: Fix some race conditions between fbmem and sysfb
Date: Thu, 7 Apr 2022 11:15:47 +0200 [thread overview]
Message-ID: <31932dda-bfd2-01ca-8ff4-9239ce0b0dd4@redhat.com> (raw)
In-Reply-To: <Yk6qwiP2kEh2M3Fm@phenom.ffwll.local>
On 4/7/22 11:11, Daniel Vetter wrote:
> On Wed, Apr 06, 2022 at 11:39:18PM +0200, Javier Martinez Canillas wrote:
[snip]
>
> Yeah it's disappointing, but no worse than the piles of hacks we have now.
>
> With the bikesheds addressed above:
>
Agree with all your comments and will address in the next version.
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>
Thanks for reviewing these patches so quickly!
--
Best regards,
Javier Martinez Canillas
Linux Engineering
Red Hat
next prev parent reply other threads:[~2022-04-07 9:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 21:39 [RESEND RFC PATCH 0/5] Fix some race conditions that exists between fbmem and sysfb Javier Martinez Canillas
2022-04-06 21:39 ` [RESEND RFC PATCH 3/5] fbdev: Restart conflicting fb removal loop when unregistering devices Javier Martinez Canillas
2022-04-07 9:08 ` Daniel Vetter
2022-04-06 21:39 ` [RESEND RFC PATCH 4/5] fbdev: Fix some race conditions between fbmem and sysfb Javier Martinez Canillas
2022-04-07 9:11 ` Daniel Vetter
2022-04-07 9:15 ` Javier Martinez Canillas [this message]
2022-04-06 21:39 ` [RESEND RFC PATCH 5/5] Revert "fbdev: Prevent probing generic drivers if a FB is already registered" Javier Martinez Canillas
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=31932dda-bfd2-01ca-8ff4-9239ce0b0dd4@redhat.com \
--to=javierm@redhat.com \
--cc=alexander.deucher@amd.com \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=sam@ravnborg.org \
--cc=thunder.leizhen@huawei.com \
--cc=tzimmermann@suse.de \
--cc=xiyuyang19@fudan.edu.cn \
/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).