From: "Noralf Trønnes" <noralf@tronnes.org>
To: Greg KH <gregkh@linuxfoundation.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
Javier Martinez Canillas <javierm@redhat.com>,
dri-devel@lists.freedesktop.org,
Maxime Ripard <mripard@kernel.org>,
stable@kernel.org, tools@linux.kernel.org
Subject: Re: [PATCH v2 0/6] drm/gud: Use the shadow plane helper
Date: Thu, 1 Dec 2022 11:00:44 +0100 [thread overview]
Message-ID: <1cb40762-5f0a-1739-1670-155f59ec7110@tronnes.org> (raw)
In-Reply-To: <Y4hB5odv9IGaq3Di@kroah.com>
Den 01.12.2022 06.55, skrev Greg KH:
> On Wed, Nov 30, 2022 at 08:26:48PM +0100, Noralf Trønnes via B4 Submission Endpoint wrote:
>> Hi,
>>
>> I have started to look at igt for testing and want to use CRC tests. To
>> implement support for this I need to move away from the simple kms
>> helper.
>>
>> When looking around for examples I came across Thomas' nice shadow
>> helper and thought, yes this is perfect for drm/gud. So I'll switch to
>> that before I move away from the simple kms helper.
>>
>> The async framebuffer flushing code path now uses a shadow buffer and
>> doesn't touch the framebuffer when it shouldn't. I have also taken the
>> opportunity to inline the synchronous flush code path and make this the
>> default flushing stategy.
>>
>> Noralf.
>>
>> Cc: Maxime Ripard <mripard@kernel.org>
>> Cc: Thomas Zimmermann <tzimmermann@suse.de>
>> Cc: dri-devel@lists.freedesktop.org
>> Signed-off-by: Noralf Trønnes <noralf@tronnes.org>
>>
>> ---
>> Changes in v2:
>> - Drop patch (Thomas):
>> drm/gem: shadow_fb_access: Prepare imported buffers for CPU access
>> - Use src as variable name for iosys_map (Thomas)
>> - Prepare imported buffer for CPU access in the driver (Thomas)
>> - New patch: make sync flushing the default (Thomas)
>> - Link to v1: https://lore.kernel.org/r/20221122-gud-shadow-plane-v1-0-9de3afa3383e@tronnes.org
>
> <formletter>
>
> This is not the correct way to submit patches for inclusion in the
> stable kernel tree. Please read:
> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> for how to do this properly.
>
> </formletter>
Care to elaborate?
Is it because stable got the whole patchset and not just the one fix
patch that cc'ed stable?
This patchset was sent using the b4 tool and I can't control this
aspect. Everyone mentioned in the patches gets the whole set.
Noralf.
next parent reply other threads:[~2022-12-01 10:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221122-gud-shadow-plane-v2-0-435037990a83@tronnes.org>
[not found] ` <Y4hB5odv9IGaq3Di@kroah.com>
2022-12-01 10:00 ` Noralf Trønnes [this message]
2022-12-01 12:12 ` [PATCH v2 0/6] drm/gud: Use the shadow plane helper Greg KH
2022-12-01 13:14 ` Noralf Trønnes
2022-12-01 13:21 ` Greg KH
2022-12-01 13:34 ` Javier Martinez Canillas
2022-12-01 14:16 ` Konstantin Ryabitsev
2022-12-01 14:20 ` Javier Martinez Canillas
2022-12-01 14:27 ` Vlastimil Babka
2022-12-01 14:32 ` Mark Brown
2023-01-05 12:35 ` Daniel Vetter
2023-01-05 16:00 ` Konstantin Ryabitsev
2022-12-01 20:52 ` Noralf Trønnes
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=1cb40762-5f0a-1739-1670-155f59ec7110@tronnes.org \
--to=noralf@tronnes.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=javierm@redhat.com \
--cc=konstantin@linuxfoundation.org \
--cc=mripard@kernel.org \
--cc=stable@kernel.org \
--cc=tools@linux.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).