amd-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Alex Deucher <alexdeucher@gmail.com>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
	"Gustavo A . R . Silva" <gustavoars@kernel.org>,
	"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] Revert "drm/radeon/si_dpm: Replace one-element array with flexible-array in struct SISLANDS_SMC_SWSTATE"
Date: Mon, 10 May 2021 17:20:54 -0400	[thread overview]
Message-ID: <CADnq5_OwNGx5XvtA8UPdGdyNmFBN9ynKESxum5=yef=XSL69JA@mail.gmail.com> (raw)
In-Reply-To: <caac4b9d-8999-8c06-80ed-0ddf1ef29c9a@embeddedor.com>

On Mon, May 10, 2021 at 4:26 AM Gustavo A. R. Silva
<gustavo@embeddedor.com> wrote:
>
> Hi Alex,
>
> I've just sent a couple of fixes for the recent radeon problems:
>
> https://lore.kernel.org/lkml/20210509224926.GA31035@embeddedor/
> https://lore.kernel.org/lkml/20210509225525.GA32045@embeddedor/
>
> So, there is no need to revert the problematic patches for radeon anymore.
>
> Sorry for the inconveniences.

Thanks for fixing these up.

Alex

> Thanks!
> --
> Gustavo
>
> On 5/5/21 08:45, Gustavo A. R. Silva wrote:
> >
> >
> > On 5/5/21 08:06, Deucher, Alexander wrote:
> >> [AMD Public Use]
> >>
> >>> -----Original Message-----
> >>> From: Gustavo A. R. Silva <gustavo@embeddedor.com>
> >>> Sent: Tuesday, May 4, 2021 6:43 PM
> >>> To: Deucher, Alexander <Alexander.Deucher@amd.com>; amd-
> >>> gfx@lists.freedesktop.org
> >>> Cc: Gustavo A . R . Silva <gustavoars@kernel.org>
> >>> Subject: Re: [PATCH] Revert "drm/radeon/si_dpm: Replace one-element
> >>> array with flexible-array in struct SISLANDS_SMC_SWSTATE"
> >>>
> >>> Hi,
> >>>
> >>> I thought it was this[1] the one causing problems[2].
> >>
> >> They are both causing problems.
> >
> > Yeah, I already know why and I'll work out a solution soon. In the meantime, both
> > should be reverted.
> >
> > These other two[1][2] also seem to have the same issue and should be reverted, too.
> > I wonder why no one has reported any problems, yet... in particular regarding this[2].
> >
> > Thanks
> > --
> > Gustavo
> >
> > [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0e1aa13ca3ffdd1e626532a3924ac80686939848
> > [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4541ea81edde6ce9a1d9be082489aca7e8e7e1dc
> >
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

      reply	other threads:[~2021-05-10 21:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-04 18:42 [PATCH] Revert "drm/radeon/si_dpm: Replace one-element array with flexible-array in struct SISLANDS_SMC_SWSTATE" Alex Deucher
2021-05-04 22:42 ` Gustavo A. R. Silva
2021-05-05 13:06   ` Deucher, Alexander
2021-05-05 13:45     ` Gustavo A. R. Silva
2021-05-09 23:02       ` Gustavo A. R. Silva
2021-05-10 21:20         ` Alex Deucher [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:
  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='CADnq5_OwNGx5XvtA8UPdGdyNmFBN9ynKESxum5=yef=XSL69JA@mail.gmail.com' \
    --to=alexdeucher@gmail.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=gustavo@embeddedor.com \
    --cc=gustavoars@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).