stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Rodrigo Vivi <rodrigo.vivi@gmail.com>
Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/vbt: Fix VBT parsing for the PSR section
Date: Tue, 30 Jul 2019 17:48:51 -0400	[thread overview]
Message-ID: <20190730214851.GF29162@sasha-vm> (raw)
In-Reply-To: <CABVU7+sbS8mw+4O1Ct8EY_5cj+fnmNFzyd6_=v2_RmCgBRA13g@mail.gmail.com>

On Tue, Jul 30, 2019 at 01:42:45PM -0700, Rodrigo Vivi wrote:
>Hi Sasha,

Hello!

>On Thu, Jul 18, 2019 at 5:45 PM Sasha Levin <sashal@kernel.org> wrote:
>>
>> Hi,
>>
>> [This is an automated email]
>
>Where did you get this patch from? Since stable needs patches merged

This bot grabs them from various mailing lists.

>on Linus tree,
>shouldn't your scripts run to try backporting only patches from there?

There's a note a few lines down that says:

    "NOTE: The patch will not be queued to stable trees until it is upstream."

Otherwise, no, there's no rule that says we can't look at patches before
they are upstream. We can't queue them up, but we sure can poke them.

The reasoning behind this is that it's easier to get replies (and
backports) from folks who are actively working on the patch now, rather
than a few weeks later when Greg sends his "FAILED:" mails and gets
ignored because said folks have moved on.

--
Thanks,
Sasha

  reply	other threads:[~2019-07-30 21:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-17 22:34 [PATCH] drm/i915/vbt: Fix VBT parsing for the PSR section Dhinakaran Pandiyan
2019-07-18 19:14 ` [Intel-gfx] " Rodrigo Vivi
     [not found] ` <20190719004526.B0CC521850@mail.kernel.org>
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 [this message]
2019-07-31 17:14       ` Vivi, Rodrigo
2019-07-31 19:23         ` Sasha Levin

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=20190730214851.GF29162@sasha-vm \
    --to=sashal@kernel.org \
    --cc=dhinakaran.pandiyan@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@gmail.com \
    --cc=stable@vger.kernel.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).