From: Stephen Rothwell <sfr@rothwell.id.au>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Shyam Sundar S K <Shyam-sundar.S-k@amd.com>,
Dave Airlie <airlied@linux.ie>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DRI <dri-devel@lists.freedesktop.org>,
Prike Liang <Prike.Liang@amd.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the amdgpu tree
Date: Sat, 24 Apr 2021 08:39:24 +1000 [thread overview]
Message-ID: <20210424083924.2e2c7cbc@elm.ozlabs.ibm.com> (raw)
In-Reply-To: <CADnq5_NGLC719T9Mx1wR+aLi8Ybwr8-ocCSYCRe=uNEBvJ+R4A@mail.gmail.com>
Hi Alex,
On Fri, 23 Apr 2021 16:36:50 -0400 Alex Deucher <alexdeucher@gmail.com> wrote:
>
> On Wed, Apr 21, 2021 at 2:40 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > On Fri, 16 Apr 2021 12:40:44 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > >
> > > After merging the amdgpu tree, today's linux-next build (powerpc
> > > ppc64_defconfig) produced this warning:
> > >
> > > drivers/pci/quirks.c: In function 'quirk_amd_nvme_fixup':
> > > drivers/pci/quirks.c:312:18: warning: unused variable 'rdev' [-Wunused-variable]
> > > 312 | struct pci_dev *rdev;
> > > | ^~~~
> > >
> > > Introduced by commit
> > >
> > > 9597624ef606 ("nvme: put some AMD PCIE downstream NVME device to simple suspend/resume path")
> >
> > I am still seeing this warning.
>
> I no longer have that patch in my tree. Was this an old build?
I guess my email crossed with the patch removal as I not longer get the
warning. Thanks.
--
Cheers,
Stephen Rothwell
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-04-23 22:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210416124044.53d4beee@canb.auug.org.au>
2021-04-21 6:40 ` linux-next: build warning after merge of the amdgpu tree Stephen Rothwell
2021-04-23 20:36 ` Alex Deucher
2021-04-23 22:39 ` Stephen Rothwell [this message]
2024-01-30 2:56 Stephen Rothwell
2024-04-21 23:56 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2024-01-30 2:54 Stephen Rothwell
2024-04-21 23:54 ` Stephen Rothwell
[not found] <20230815210747.6c409362@canb.auug.org.au>
2023-08-16 1:57 ` Stephen Rothwell
[not found] <20221026121428.5181969a@canb.auug.org.au>
2023-07-11 23:12 ` Stephen Rothwell
2023-06-09 4:02 Stephen Rothwell
2023-06-07 2:45 Stephen Rothwell
[not found] <20210322170014.3e022928@canb.auug.org.au>
2021-04-21 6:15 ` Stephen Rothwell
[not found] <20210311220033.7c5fe548@canb.auug.org.au>
2021-04-21 6:10 ` Stephen Rothwell
[not found] <20210115120014.4211dec6@canb.auug.org.au>
[not found] ` <20210120171501.61aa0786@canb.auug.org.au>
2021-01-21 0:53 ` Stephen Rothwell
2021-01-21 3:07 ` Alex Deucher
2021-01-21 8:32 ` Daniel Vetter
[not found] <20201117154514.2c378d99@canb.auug.org.au>
2020-12-14 19:56 ` Stephen Rothwell
2020-12-15 2:49 ` Stephen Rothwell
2019-12-18 23:18 Stephen Rothwell
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=20210424083924.2e2c7cbc@elm.ozlabs.ibm.com \
--to=sfr@rothwell.id.au \
--cc=Prike.Liang@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=airlied@linux.ie \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).