All of lore.kernel.org
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
Cc: "sashal@kernel.org" <sashal@kernel.org>,
	"kernel@gpiccoli.net" <kernel@gpiccoli.net>,
	"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"kernel-dev@igalia.com" <kernel-dev@igalia.com>,
	"Deucher, Alexander" <Alexander.Deucher@amd.com>,
	"Zhu, James" <James.Zhu@amd.com>, "Liu, Leo" <Leo.Liu@amd.com>
Subject: Re: [PATCH 6.1.y] drm/amdgpu/vcn: Disable indirect SRAM on Vangogh broken BIOSes
Date: Thu, 20 Apr 2023 17:02:49 +0200	[thread overview]
Message-ID: <ZEFUGSlqQu3v8ryf@kroah.com> (raw)
In-Reply-To: <94b63d19-4151-c294-50eb-c325ea9c699f@igalia.com>

On Thu, Apr 20, 2023 at 09:59:17AM -0300, Guilherme G. Piccoli wrote:
> On 20/04/2023 09:42, gregkh@linuxfoundation.org wrote:
> > [...]
> >> @Greg, can you pick this one? Thanks!
> > 
> > Which "one" are you referring to here?
> > 
> > confused,
> > 
> > greg k-h
> 
> This one, sent in this email thread.

I don't have "this email thread" anymore, remember, some of us get
thousand+ emails a day...

> The title of the patch is "drm/amdgpu/vcn: Disable indirect SRAM on
> Vangogh broken BIOSes", target is 6.1.y and (one of the) upstream
> hash(es) is 542a56e8eb44 heh

But that commit says it fixes a problem in the 6.2 tree, why is this
relevant for 6.1.y?

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"sashal@kernel.org" <sashal@kernel.org>,
	"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
	"Zhu, James" <James.Zhu@amd.com>, "Liu, Leo" <Leo.Liu@amd.com>,
	"kernel@gpiccoli.net" <kernel@gpiccoli.net>,
	"kernel-dev@igalia.com" <kernel-dev@igalia.com>
Subject: Re: [PATCH 6.1.y] drm/amdgpu/vcn: Disable indirect SRAM on Vangogh broken BIOSes
Date: Thu, 20 Apr 2023 17:02:49 +0200	[thread overview]
Message-ID: <ZEFUGSlqQu3v8ryf@kroah.com> (raw)
In-Reply-To: <94b63d19-4151-c294-50eb-c325ea9c699f@igalia.com>

On Thu, Apr 20, 2023 at 09:59:17AM -0300, Guilherme G. Piccoli wrote:
> On 20/04/2023 09:42, gregkh@linuxfoundation.org wrote:
> > [...]
> >> @Greg, can you pick this one? Thanks!
> > 
> > Which "one" are you referring to here?
> > 
> > confused,
> > 
> > greg k-h
> 
> This one, sent in this email thread.

I don't have "this email thread" anymore, remember, some of us get
thousand+ emails a day...

> The title of the patch is "drm/amdgpu/vcn: Disable indirect SRAM on
> Vangogh broken BIOSes", target is 6.1.y and (one of the) upstream
> hash(es) is 542a56e8eb44 heh

But that commit says it fixes a problem in the 6.2 tree, why is this
relevant for 6.1.y?

thanks,

greg k-h

  reply	other threads:[~2023-04-20 15:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18 22:15 [PATCH 6.1.y] drm/amdgpu/vcn: Disable indirect SRAM on Vangogh broken BIOSes Guilherme G. Piccoli
2023-04-18 22:15 ` Guilherme G. Piccoli
2023-04-19 13:16 ` Deucher, Alexander
2023-04-19 13:16   ` Deucher, Alexander
2023-04-19 14:14   ` Guilherme G. Piccoli
2023-04-19 14:14     ` Guilherme G. Piccoli
2023-04-19 20:04     ` Deucher, Alexander
2023-04-19 20:04       ` Deucher, Alexander
2023-04-20 12:36       ` Guilherme G. Piccoli
2023-04-20 12:36         ` Guilherme G. Piccoli
2023-04-20 12:42         ` gregkh
2023-04-20 12:42           ` gregkh
2023-04-20 12:59           ` Guilherme G. Piccoli
2023-04-20 12:59             ` Guilherme G. Piccoli
2023-04-20 15:02             ` gregkh [this message]
2023-04-20 15:02               ` gregkh
2023-04-20 15:26               ` Alex Deucher
2023-04-20 15:26                 ` Alex Deucher
2023-04-20 15:36               ` Guilherme G. Piccoli
2023-04-20 15:36                 ` Guilherme G. Piccoli
2023-04-20 15:56                 ` gregkh
2023-04-20 15:56                   ` gregkh
2023-04-20 16:45                   ` Guilherme G. Piccoli
2023-04-20 16:45                     ` Guilherme G. Piccoli
2023-04-22 15:19 ` Greg KH
2023-04-22 15:19   ` Greg KH

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=ZEFUGSlqQu3v8ryf@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Alexander.Deucher@amd.com \
    --cc=James.Zhu@amd.com \
    --cc=Leo.Liu@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=gpiccoli@igalia.com \
    --cc=kernel-dev@igalia.com \
    --cc=kernel@gpiccoli.net \
    --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.