linux-firmware.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@kernel.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Linux Firmware <linux-firmware@kernel.org>,
	 "Limonciello, Mario" <Mario.Limonciello@amd.com>,
	Aurabindo Pillai <aurabindo.pillai@amd.com>
Subject: Re: amdgpu firmware updates
Date: Mon, 24 Jul 2023 10:46:23 -0400	[thread overview]
Message-ID: <CA+5PVA7eFWqEis8OeSLEmoi=qZhEMftwHF6c4vgRjdvaM9BdZQ@mail.gmail.com> (raw)
In-Reply-To: <CADnq5_MnJQ-EYvXR4F1rcUgEOinpncwTaScUSRjTAAj_p_r=dQ@mail.gmail.com>

Applied and pushed out.  Thanks for the quick response!

josh

On Mon, Jul 24, 2023 at 10:39 AM Alex Deucher <alexdeucher@gmail.com> wrote:
>
> Fixed up.  New patches attached.  Sorry about that.
>
> Alex
>
> On Mon, Jul 24, 2023 at 8:25 AM Josh Boyer <jwboyer@kernel.org> wrote:
> >
> > The first patch generates:
> >
> > [jwboyer@vader linux-firmware]$ ./check_whence.py
> > E: amdgpu/gc_11_0_3_mes.bin listed in WHENCE does not exist
> > [jwboyer@vader linux-firmware]$
> >
> > Can you fix it up and resubmit?
> >
> > josh
> >
> > On Fri, Jul 14, 2023 at 10:21 AM Alex Deucher <alexdeucher@gmail.com> wrote:
> > >
> > > Hi,
> > >
> > > New amdgpu firmware.  Please apply!
> > >
> > > Thanks,
> > >
> > > Alex

  reply	other threads:[~2023-07-24 14:46 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADnq5_MQM1sG50oq4FoOTVOrg+b+Q5is7X3rpbwSFZu7s7ZhSg@mail.gmail.com>
2023-07-24 12:24 ` amdgpu firmware updates Josh Boyer
2023-07-24 14:37   ` Alex Deucher
2023-07-24 14:46     ` Josh Boyer [this message]
2023-05-23 15:36 Deucher, Alexander
2023-05-23 17:06 ` Josh Boyer
     [not found] <CADnq5_O2jXZWCf=PYAOciwOi9ouH5vjw=Lce-f_5-SAayCKreA@mail.gmail.com>
2022-05-16 19:26 ` Josh Boyer
  -- strict thread matches above, loose matches on Subject: below --
2022-04-26 15:15 Alex Deucher
2022-05-02 12:26 ` Josh Boyer
2022-05-02 15:59   ` Alex Deucher
     [not found] <CADnq5_MtfxOyoEOn-v8Gwr70FXinTtgaVsHf3hVXWxStOhSBSw@mail.gmail.com>
2021-08-12 13:19 ` Josh Boyer
2021-06-28 17:50 Alex Deucher
2021-06-28 19:25 ` Alex Deucher
2021-06-29 11:26   ` Josh Boyer
2021-04-21  0:52 Alex Deucher
2021-04-21 11:14 ` Josh Boyer
2021-04-21 14:37   ` Alex Deucher
2021-03-18 21:06 Alex Deucher
2021-03-22 12:09 ` Josh Boyer
2021-03-22 13:17   ` Alex Deucher
2020-09-30 15:11 Alex Deucher
2020-10-05 12:01 ` Josh Boyer
2020-08-20  2:57 Alex Deucher
2020-08-24 20:15 ` Josh Boyer
2020-08-24 20:16   ` Alex Deucher
2020-08-04 17:24 Alex Deucher
2020-08-07 12:17 ` Josh Boyer
2020-08-07 15:17   ` Alex Deucher
2020-06-29 16:54 Alex Deucher
2020-06-29 19:11 ` Josh Boyer
2020-06-29 19:53   ` Alex Deucher
2020-06-15 21:47 Alex Deucher
2020-06-19 12:37 ` Josh Boyer
2020-06-19 14:52   ` Alex Deucher
2020-06-29 18:31     ` Alex Deucher
2020-06-29 18:43       ` Alex Deucher
2020-06-29 19:10         ` Josh Boyer
     [not found] <CADnq5_Pm_HJSM4Op1zyYUvoK2VN5=+ZnrkwqtYZPGOwiDjasPA@mail.gmail.com>
2020-04-17 15:27 ` Josh Boyer
2020-04-17 17:16   ` Alex Deucher
2020-03-06 18:48 Alex Deucher
2020-03-09 17:53 ` Josh Boyer
2020-02-17 15:11 Alex Deucher
2020-02-19 12:32 ` Josh Boyer

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='CA+5PVA7eFWqEis8OeSLEmoi=qZhEMftwHF6c4vgRjdvaM9BdZQ@mail.gmail.com' \
    --to=jwboyer@kernel.org \
    --cc=Mario.Limonciello@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=aurabindo.pillai@amd.com \
    --cc=linux-firmware@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).