All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@gmail.com>
To: Sasha Levin <sashal@kernel.org>
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 13:42:45 -0700	[thread overview]
Message-ID: <CABVU7+sbS8mw+4O1Ct8EY_5cj+fnmNFzyd6_=v2_RmCgBRA13g@mail.gmail.com> (raw)
In-Reply-To: <20190719004526.B0CC521850@mail.kernel.org>

Hi Sasha,

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
on Linus tree,
shouldn't your scripts run to try backporting only patches from there?

Thanks,
Rodrigo.

>
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: 88a0d9606aff drm/i915/vbt: Parse and use the new field with PSR2 TP2/3 wakeup time.
>
> The bot has tested the following trees: v5.2.1.
> v5.2.1: Failed to apply! Possible dependencies:
>     231dcffc234f ("drm/i915/bios: add BDB block comments before definitions")
>     843444ed1301 ("drm/i915/bios: sort BDB block definitions using block ID")
>     f87f6599c843 ("drm/i915/bios: reserve struct bdb_ prefix for BDB blocks")
>
>
> NOTE: The patch will not be queued to stable trees until it is upstream.
>
> How should we proceed with this patch?
>
> --
> Thanks,
> Sasha
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx



-- 
Rodrigo Vivi
Blog: http://blog.vivi.eng.br

  parent reply	other threads:[~2019-07-30 20:42 UTC|newest]

Thread overview: 27+ 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-17 22:34 ` Dhinakaran Pandiyan
2019-07-17 23:19 ` ✓ Fi.CI.BAT: success for drm/i915/vbt: Fix VBT parsing for the PSR section (rev3) Patchwork
2019-07-18 19:14 ` [Intel-gfx] [PATCH] drm/i915/vbt: Fix VBT parsing for the PSR section Rodrigo Vivi
2019-07-19  0:45 ` Sasha Levin
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:27         ` Souza, Jose
2019-07-24 17:40         ` [Intel-gfx] " Rodrigo Vivi
2019-07-24 17:40           ` Rodrigo Vivi
2019-07-30 15:19           ` [Intel-gfx] " Rodrigo Vivi
2019-07-30 15:19             ` Rodrigo Vivi
2019-07-30 15:27             ` [Intel-gfx] " 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 16:56                     ` Rodrigo Vivi
2019-07-30 17:08                     ` Greg KH
2019-07-30 18:24                       ` Pandiyan, Dhinakaran
2019-07-30 20:42   ` Rodrigo Vivi [this message]
2019-07-30 21:48     ` [Intel-gfx] [PATCH] " Sasha Levin
2019-07-30 21:48       ` Sasha Levin
2019-07-31 17:14       ` [Intel-gfx] " Vivi, Rodrigo
2019-07-31 17:14         ` Vivi, Rodrigo
2019-07-31 19:23         ` [Intel-gfx] " Sasha Levin
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='CABVU7+sbS8mw+4O1Ct8EY_5cj+fnmNFzyd6_=v2_RmCgBRA13g@mail.gmail.com' \
    --to=rodrigo.vivi@gmail.com \
    --cc=dhinakaran.pandiyan@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=sashal@kernel.org \
    --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 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.