archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <>
To: "Vivi, Rodrigo" <>
Cc: Rodrigo Vivi <>,
	intel-gfx <>,
	"Pandiyan, Dhinakaran" <>,
	"" <>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/vbt: Fix VBT parsing for the PSR section
Date: Wed, 31 Jul 2019 15:23:31 -0400	[thread overview]
Message-ID: <20190731192331.GA17697@sasha-vm> (raw)
In-Reply-To: <>

On Wed, Jul 31, 2019 at 05:14:38PM +0000, Vivi, Rodrigo wrote:
>> On Jul 30, 2019, at 2:48 PM, Sasha Levin <> wrote:
>> rather
>> than a few weeks later when Greg sends his "FAILED:" mails and gets
>> ignored because said folks have moved on.
>however this could potentially cause extra work and confusion like we can see on this
>thread where the developer immediately responded to your email and sent the
>backported patch to the stable mailing list.
>Maybe it is just because we are used to Greg's failed to apply email or maybe
>it was just a matter of education...

I think that there were a few things here that ended up causing
confusion, but I'm not quite sure how to address them.

I think that stable should have a clearer rules as to how backports
should be sent. Right now we weed through mails to stable@ to figure out
what are backport requests, what are upstream patches, and what are just
confused folks.

We have gotten pretty good at this, but still not perfect...

>But I wonder if there isn't something that could be improved on the automated
>message here. Some message clearly stating:
>- No action required at this point

One *could* send a backport at this point. My understanding is that when
Greg sees a failure to apply a commit tagged for stable he'll grep
through his mailbox, hopefully finding the backport as a result of this
bot bugging people.

>- you can work to prepare the backport in advance
>-  don't send it to stable before requested by Greg

Why not? I think it's fine to put it on the mailing list, specially
under the same thread, and let us deal with it after the patch goes


      reply	other threads:[~2019-07-31 19:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-17 22:34 Dhinakaran Pandiyan
2019-07-18 19:14 ` [Intel-gfx] " Rodrigo Vivi
     [not found] ` <>
2019-07-22 23:13   ` [PATCH stable v5.2] " Dhinakaran Pandiyan
2019-07-24 12:06     ` Greg KH
2019-07-24 17:27       ` Souza, Jose
2019-07-24 17:40         ` [Intel-gfx] " Rodrigo Vivi
2019-07-30 15:19           ` Rodrigo Vivi
2019-07-30 15:27             ` Greg KH
2019-07-30 16:22               ` Rodrigo Vivi
2019-07-30 16:27                 ` Greg KH
2019-07-30 16:56                   ` Rodrigo Vivi
2019-07-30 17:08                     ` Greg KH
2019-07-30 18:24                       ` Pandiyan, Dhinakaran
2019-07-30 20:42   ` [Intel-gfx] [PATCH] " Rodrigo Vivi
2019-07-30 21:48     ` Sasha Levin
2019-07-31 17:14       ` Vivi, Rodrigo
2019-07-31 19:23         ` Sasha Levin [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190731192331.GA17697@sasha-vm \ \ \ \ \ \ \
    --subject='Re: [Intel-gfx] [PATCH] drm/i915/vbt: Fix VBT parsing for the PSR section' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).