From: Chen-Yu Tsai <wens@kernel.org>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: linux-hyperv@vger.kernel.org,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
nouveau@lists.freedesktop.org,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
virtualization@lists.linux-foundation.org,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
amd-gfx@lists.freedesktop.org, Daniel Vetter <daniel@ffwll.ch>,
spice-devel@lists.freedesktop.org, linux-tegra@vger.kernel.org,
airlied@redhat.com,
"open list:ARM/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>,
freedreno@lists.freedesktop.org, linux-sunxi@lists.linux.dev,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [Nouveau] [PATCH] drm/aperture: Pass DRM driver structure instead of driver name
Date: Tue, 29 Jun 2021 23:59:33 +0800 [thread overview]
Message-ID: <CAGb2v66wYxs7u1AubriRokPFh72ZONMxGgmGNPB5mFLOZNw_3Q@mail.gmail.com> (raw)
In-Reply-To: <20210629135833.22679-1-tzimmermann@suse.de>
On Tue, Jun 29, 2021 at 9:58 PM Thomas Zimmermann <tzimmermann@suse.de> wrote:
>
> Print the name of the DRM driver when taking over fbdev devices. Makes
> the output to dmesg more consistent. Note that the driver name is only
> used for printing a string to the kernel log. No UAPI is affected by this
> change.
>
> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
> ---
> drivers/gpu/drm/sun4i/sun4i_drv.c | 2 +-
Acked-by: Chen-Yu Tsai <wens@csie.org>
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2021-06-30 2:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 13:58 [Nouveau] [PATCH] drm/aperture: Pass DRM driver structure instead of driver name Thomas Zimmermann
2021-06-29 15:32 ` Das, Nirmoy
2021-06-29 15:59 ` Chen-Yu Tsai [this message]
2021-06-29 17:03 ` Neil Armstrong
2021-08-05 20:37 ` Dmitry Baryshkov
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=CAGb2v66wYxs7u1AubriRokPFh72ZONMxGgmGNPB5mFLOZNw_3Q@mail.gmail.com \
--to=wens@kernel.org \
--cc=airlied@redhat.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=spice-devel@lists.freedesktop.org \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux-foundation.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 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).