All of lore.kernel.org
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javierm@redhat.com>
To: "Greg KH" <gregkh@linuxfoundation.org>,
	"Noralf Trønnes" <noralf@tronnes.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	dri-devel@lists.freedesktop.org,
	Maxime Ripard <mripard@kernel.org>,
	tools@linux.kernel.org
Subject: Re: [PATCH v2 0/6] drm/gud: Use the shadow plane helper
Date: Thu, 1 Dec 2022 14:34:41 +0100	[thread overview]
Message-ID: <e57deac6-5344-3f81-8ef5-55dd28b8c363@redhat.com> (raw)
In-Reply-To: <Y4iqR94aGFa3NahQ@kroah.com>

Hello Greg,

On 12/1/22 14:21, Greg KH wrote:

[...]

>>>> This patchset was sent using the b4 tool and I can't control this
>>>> aspect. Everyone mentioned in the patches gets the whole set.
>>>
>>> Fair enough, but watch out, bots will report this as being a problem as
>>> they can't always read through all patches in a series to notice this...
>>>
>>
>> Konstantin,
>>
>> Can you add a rule in b4 to exclude stable@vger.kernel.org
>> (stable@kernel.org as well?) from getting the whole patchset?
> 
> stable@kernel.org is a pipe to /dev/null so that's not needed to be
> messed with.
> 
> As for this needing special casing in b4, it's rare that you send out a
> patch series and only want 1 or 2 of them in stable, right?
>

Not really, it's very common for a patch-series to contain fixes (that could
go to stable if applicable) and change that are not suitable for stable. The
problem as Noralf mentioned is that the b4 tool doesn't seem to allow Cc'ing
individual patches to different recipients, and everyone get the whole set.

So either b4 needs to have this support, exclude stable@vger.kernel.org when
sending a set or stable@vger.kernel.org ignore patches without a Fixes: tag.

-- 
Best regards,

Javier Martinez Canillas
Core Platforms
Red Hat


WARNING: multiple messages have this Message-ID (diff)
From: Javier Martinez Canillas <javierm@redhat.com>
To: "Greg KH" <gregkh@linuxfoundation.org>,
	"Noralf Trønnes" <noralf@tronnes.org>
Cc: tools@linux.kernel.org, dri-devel@lists.freedesktop.org,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: [PATCH v2 0/6] drm/gud: Use the shadow plane helper
Date: Thu, 1 Dec 2022 14:34:41 +0100	[thread overview]
Message-ID: <e57deac6-5344-3f81-8ef5-55dd28b8c363@redhat.com> (raw)
In-Reply-To: <Y4iqR94aGFa3NahQ@kroah.com>

Hello Greg,

On 12/1/22 14:21, Greg KH wrote:

[...]

>>>> This patchset was sent using the b4 tool and I can't control this
>>>> aspect. Everyone mentioned in the patches gets the whole set.
>>>
>>> Fair enough, but watch out, bots will report this as being a problem as
>>> they can't always read through all patches in a series to notice this...
>>>
>>
>> Konstantin,
>>
>> Can you add a rule in b4 to exclude stable@vger.kernel.org
>> (stable@kernel.org as well?) from getting the whole patchset?
> 
> stable@kernel.org is a pipe to /dev/null so that's not needed to be
> messed with.
> 
> As for this needing special casing in b4, it's rare that you send out a
> patch series and only want 1 or 2 of them in stable, right?
>

Not really, it's very common for a patch-series to contain fixes (that could
go to stable if applicable) and change that are not suitable for stable. The
problem as Noralf mentioned is that the b4 tool doesn't seem to allow Cc'ing
individual patches to different recipients, and everyone get the whole set.

So either b4 needs to have this support, exclude stable@vger.kernel.org when
sending a set or stable@vger.kernel.org ignore patches without a Fixes: tag.

-- 
Best regards,

Javier Martinez Canillas
Core Platforms
Red Hat


  reply	other threads:[~2022-12-01 13:34 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30 19:26 [PATCH v2 0/6] drm/gud: Use the shadow plane helper Noralf Trønnes
2022-11-30 19:26 ` Noralf Trønnes via B4 Submission Endpoint
2022-11-30 19:26 ` [PATCH v2 1/6] drm/gud: Fix UBSAN warning Noralf Trønnes
2022-11-30 19:26   ` Noralf Trønnes via B4 Submission Endpoint
2022-11-30 19:26 ` [PATCH v2 2/6] drm/gud: Don't retry a failed framebuffer flush Noralf Trønnes
2022-11-30 19:26   ` Noralf Trønnes via B4 Submission Endpoint
2022-11-30 19:26 ` [PATCH v2 3/6] drm/gud: Split up gud_flush_work() Noralf Trønnes
2022-11-30 19:26   ` Noralf Trønnes via B4 Submission Endpoint
2022-11-30 19:26 ` [PATCH v2 4/6] drm/gud: Prepare buffer for CPU access in gud_flush_work() Noralf Trønnes
2022-11-30 19:26   ` Noralf Trønnes via B4 Submission Endpoint
2022-12-01  8:51   ` Thomas Zimmermann
2022-11-30 19:26 ` [PATCH v2 5/6] drm/gud: Use the shadow plane helper Noralf Trønnes
2022-11-30 19:26   ` Noralf Trønnes via B4 Submission Endpoint
2022-12-01  8:55   ` Thomas Zimmermann
2022-11-30 19:26 ` [PATCH v2 6/6] drm/gud: Enable synchronous flushing by default Noralf Trønnes
2022-11-30 19:26   ` Noralf Trønnes via B4 Submission Endpoint
2022-12-01  8:57   ` Thomas Zimmermann
2022-12-01  5:55 ` [PATCH v2 0/6] drm/gud: Use the shadow plane helper Greg KH
2022-12-01 10:00   ` Noralf Trønnes
2022-12-01 10:00     ` Noralf Trønnes
2022-12-01 12:12     ` Greg KH
2022-12-01 12:12       ` Greg KH
2022-12-01 13:14       ` Noralf Trønnes
2022-12-01 13:14         ` Noralf Trønnes
2022-12-01 13:21         ` Greg KH
2022-12-01 13:21           ` Greg KH
2022-12-01 13:34           ` Javier Martinez Canillas [this message]
2022-12-01 13:34             ` Javier Martinez Canillas
2022-12-01 14:16             ` Konstantin Ryabitsev
2022-12-01 14:16               ` Konstantin Ryabitsev
2022-12-01 14:20               ` Javier Martinez Canillas
2022-12-01 14:20                 ` Javier Martinez Canillas
2022-12-01 14:27               ` Vlastimil Babka
2022-12-01 14:27                 ` Vlastimil Babka
2022-12-01 14:32                 ` Mark Brown
2022-12-01 14:32                   ` Mark Brown
2023-01-05 12:35                   ` Daniel Vetter
2023-01-05 12:35                     ` Daniel Vetter
2023-01-05 16:00                     ` Konstantin Ryabitsev
2023-01-05 16:00                       ` Konstantin Ryabitsev
2022-12-01 20:52               ` Noralf Trønnes
2022-12-01 20:52                 ` Noralf Trønnes
2022-12-06 15:57 ` 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=e57deac6-5344-3f81-8ef5-55dd28b8c363@redhat.com \
    --to=javierm@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=mripard@kernel.org \
    --cc=noralf@tronnes.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 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.