All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Mark Brown <broonie@kernel.org>
Cc: "Vlastimil Babka" <vbabka@suse.cz>,
	tools@linux.kernel.org, "Greg KH" <gregkh@linuxfoundation.org>,
	"Javier Martinez Canillas" <javierm@redhat.com>,
	dri-devel@lists.freedesktop.org,
	"Noralf Trønnes" <noralf@tronnes.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, 5 Jan 2023 13:35:37 +0100	[thread overview]
Message-ID: <Y7bEGaZol7jFuHwR@phenom.ffwll.local> (raw)
In-Reply-To: <Y4i672D3GHu2xPS5@sirena.org.uk>

On Thu, Dec 01, 2022 at 02:32:15PM +0000, Mark Brown wrote:
> On Thu, Dec 01, 2022 at 03:27:32PM +0100, Vlastimil Babka wrote:
> 
> > I usually do that with git send-email and a custom --cc-cmd script, but
> > additionally it sends the cover letter also to everyone that's on any
> > individual patch's Cc, so everyone gets at least the cover letter + their
> > specific patch(es).
> 
> > But that extra logic could be optional.
> 
> Yeah, without the cover letter if you've just got an individual patch it
> can be unclear what's going on with dependencies and so on for getting
> the patches merged.

+1 on including the cover letter for any recipient. If b4 can do this
right by default, that would be a really good reason for me to look into
it and switch.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch>
To: Mark Brown <broonie@kernel.org>
Cc: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>,
	"Greg KH" <gregkh@linuxfoundation.org>,
	"Javier Martinez Canillas" <javierm@redhat.com>,
	dri-devel@lists.freedesktop.org,
	"Noralf Trønnes" <noralf@tronnes.org>,
	"Vlastimil Babka" <vbabka@suse.cz>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	tools@linux.kernel.org
Subject: Re: [PATCH v2 0/6] drm/gud: Use the shadow plane helper
Date: Thu, 5 Jan 2023 13:35:37 +0100	[thread overview]
Message-ID: <Y7bEGaZol7jFuHwR@phenom.ffwll.local> (raw)
In-Reply-To: <Y4i672D3GHu2xPS5@sirena.org.uk>

On Thu, Dec 01, 2022 at 02:32:15PM +0000, Mark Brown wrote:
> On Thu, Dec 01, 2022 at 03:27:32PM +0100, Vlastimil Babka wrote:
> 
> > I usually do that with git send-email and a custom --cc-cmd script, but
> > additionally it sends the cover letter also to everyone that's on any
> > individual patch's Cc, so everyone gets at least the cover letter + their
> > specific patch(es).
> 
> > But that extra logic could be optional.
> 
> Yeah, without the cover letter if you've just got an individual patch it
> can be unclear what's going on with dependencies and so on for getting
> the patches merged.

+1 on including the cover letter for any recipient. If b4 can do this
right by default, that would be a really good reason for me to look into
it and switch.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

  reply	other threads:[~2023-01-05 12:35 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 via B4 Submission Endpoint
2022-11-30 19:26 ` Noralf Trønnes
2022-11-30 19:26 ` [PATCH v2 1/6] drm/gud: Fix UBSAN warning Noralf Trønnes via B4 Submission Endpoint
2022-11-30 19:26   ` Noralf Trønnes
2022-11-30 19:26 ` [PATCH v2 2/6] drm/gud: Don't retry a failed framebuffer flush Noralf Trønnes via B4 Submission Endpoint
2022-11-30 19:26   ` Noralf Trønnes
2022-11-30 19:26 ` [PATCH v2 3/6] drm/gud: Split up gud_flush_work() Noralf Trønnes via B4 Submission Endpoint
2022-11-30 19:26   ` Noralf Trønnes
2022-11-30 19:26 ` [PATCH v2 4/6] drm/gud: Prepare buffer for CPU access in gud_flush_work() Noralf Trønnes via B4 Submission Endpoint
2022-11-30 19:26   ` Noralf Trønnes
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 via B4 Submission Endpoint
2022-11-30 19:26   ` Noralf Trønnes
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 via B4 Submission Endpoint
2022-11-30 19:26   ` Noralf Trønnes
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
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 [this message]
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=Y7bEGaZol7jFuHwR@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=broonie@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=javierm@redhat.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=noralf@tronnes.org \
    --cc=tools@linux.kernel.org \
    --cc=tzimmermann@suse.de \
    --cc=vbabka@suse.cz \
    /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.