From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Brian Norris <briannorris@chromium.org>,
dri-devel@lists.freedesktop.org, Borislav Petkov <bp@alien8.de>,
Julius Werner <jwerner@chromium.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
chrome-platform@lists.linux.dev, intel-gfx@lists.freedesktop.org,
Hugues Bruant <hugues.bruant@gmail.com>,
Alex Deucher <alexander.deucher@amd.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
Helge Deller <deller@gmx.de>, Jani Nikula <jani.nikula@intel.com>
Subject: Re: [PATCH v4 0/2] firmware: Avoid coreboot and sysfb to register a pdev for same framebuffer
Date: Thu, 19 Sep 2024 07:40:47 +0000 [thread overview]
Message-ID: <ZuvVf5XRMqjD8G9T@google.com> (raw)
In-Reply-To: <20240916110040.1688511-1-javierm@redhat.com>
On Mon, Sep 16, 2024 at 01:00:24PM +0200, Javier Martinez Canillas wrote:
> The patches have only been compiled tested because I don't have access to
> a coreboot machine. Please let me know if you plan to merge both patches
> through the chrome-platforms tree or if you prefer to get merged through
> the drm-misc tree.
>
> [...]
> Javier Martinez Canillas (2):
> firmware: sysfb: Add a sysfb_handles_screen_info() helper function
> firmware: coreboot: Don't register a pdev if screen_info data is
> present
I'll queue both patches through the chrome-platform tree for v6.13 if there is
no objections.
next prev parent reply other threads:[~2024-09-19 7:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 11:00 [PATCH v4 0/2] firmware: Avoid coreboot and sysfb to register a pdev for same framebuffer Javier Martinez Canillas
2024-09-16 11:00 ` [PATCH v4 1/2] firmware: sysfb: Add a sysfb_handles_screen_info() helper function Javier Martinez Canillas
2024-09-16 14:26 ` Thomas Zimmermann
2024-09-16 11:00 ` [PATCH v4 2/2] firmware: coreboot: Don't register a pdev if screen_info data is present Javier Martinez Canillas
2024-09-19 7:40 ` Tzung-Bi Shih [this message]
2024-09-19 8:27 ` [PATCH v4 0/2] firmware: Avoid coreboot and sysfb to register a pdev for same framebuffer Javier Martinez Canillas
2024-09-30 1:44 ` Tzung-Bi Shih
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=ZuvVf5XRMqjD8G9T@google.com \
--to=tzungbi@kernel.org \
--cc=alexander.deucher@amd.com \
--cc=bp@alien8.de \
--cc=briannorris@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=dan.carpenter@linaro.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=hugues.bruant@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=javierm@redhat.com \
--cc=jwerner@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tzimmermann@suse.de \
/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