From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Damien Le Moal <damien.lemoal@opensource•wdc.com>
Cc: Serge Semin <Sergey.Semin@baikalelectronics•ru>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build warning after merge of the libata tree
Date: Mon, 19 Sep 2022 12:40:34 +1000 [thread overview]
Message-ID: <20220919124034.58670a27@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 496 bytes --]
Hi all,
After merging the libata tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
drivers/ata/ahci_st.c: In function 'st_ahci_probe':
drivers/ata/ahci_st.c:147:24: warning: unused variable 'dev' [-Wunused-variable]
147 | struct device *dev = &pdev->dev;
| ^~~
Introduced by commit
3f74cd046fbe ("ata: libahci_platform: Parse ports-implemented property in resources getter")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-09-19 2:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 2:40 Stephen Rothwell [this message]
2022-09-19 8:01 ` linux-next: build warning after merge of the libata tree Damien Le Moal
2022-09-19 23:56 ` Damien Le Moal
2022-09-20 19:25 ` Serge Semin
-- strict thread matches above, loose matches on Subject: below --
2022-06-20 0:34 Stephen Rothwell
2022-06-20 0:43 ` Damien Le Moal
2022-06-20 8:21 ` Stephen Rothwell
2022-06-20 8:53 ` Damien Le Moal
2022-06-20 10:57 ` Sergey Shtylyov
2022-06-20 11:07 ` Damien Le Moal
2022-06-20 20:07 ` Sergey Shtylyov
2022-06-20 20:08 ` Sergey Shtylyov
2018-03-20 4:57 Stephen Rothwell
2018-03-20 4:59 ` Richard Zhu
2018-02-13 3:04 Stephen Rothwell
2018-02-13 14:42 ` Tejun Heo
2018-01-18 4:26 Stephen Rothwell
2017-06-28 5:51 Stephen Rothwell
2017-06-28 18:28 ` Tejun Heo
2012-02-13 5:27 Stephen Rothwell
2012-02-24 3:08 ` Stephen Rothwell
2012-02-24 4:06 ` Jeff Garzik
2012-02-24 4:14 ` Stephen Rothwell
2012-02-24 12:22 ` Stephen Rothwell
2012-02-24 17:01 ` Jeff Garzik
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=20220919124034.58670a27@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=Sergey.Semin@baikalelectronics$(echo .)ru \
--cc=damien.lemoal@opensource$(echo .)wdc.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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