From: Stephen Rothwell <sfr@canb.auug.org.au>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Sujit Reddy Thumma <sthumma@codeaurora.org>,
Santosh Y <santoshsy@gmail.com>, Tejun Heo <tj@kernel.org>
Subject: linux-next: build warning after merge of the scsi tree
Date: Mon, 2 Sep 2013 18:28:17 +1000 [thread overview]
Message-ID: <20130902182817.87a961aa251604b630620028@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 685 bytes --]
Hi James,
After merging the scsi tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/scsi/ufs/ufshcd.c: In function 'ufshcd_eh_host_reset_handler':
drivers/scsi/ufs/ufshcd.c:2740:3: warning: 'flush_work_sync' is deprecated (declared at /scratch/sfr/next/include/linux/workqueue.h:624) [-Wdeprecated-declarations]
flush_work_sync(&hba->eh_work);
^
Introduced by commit c1e846ab4422 ("[SCSI] ufs: Fix device and host reset
methods"). flush_work_sync was deprecated by commit 43829731dd37
("workqueue: deprecate flush[_delayed]_work_sync()") before v3.7-rc1.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-09-02 8:28 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 8:28 Stephen Rothwell [this message]
2013-09-04 9:18 ` linux-next: build warning after merge of the scsi tree Sujit Reddy Thumma
2013-09-04 9:54 ` Sujit Reddy Thumma
-- strict thread matches above, loose matches on Subject: below --
2021-08-20 6:14 Stephen Rothwell
2021-08-20 6:30 ` Masahiro Yamada
2021-03-18 5:54 Stephen Rothwell
[not found] <CGME20200625034139epcas5p126a29921cc3f751528786b00f4b2828b@epcas5p1.samsung.com>
2020-06-25 3:41 ` Stephen Rothwell
2020-06-25 14:29 ` Alim Akhtar
2019-11-07 4:01 Stephen Rothwell
2019-11-07 15:51 ` Bart Van Assche
2019-11-08 23:02 ` James Smart
2019-06-20 6:10 Stephen Rothwell
2019-05-31 3:36 Stephen Rothwell
2019-06-03 20:29 ` Tyrel Datwyler
2019-06-03 23:37 ` Tyrel Datwyler
2019-04-05 3:25 Stephen Rothwell
2019-04-05 4:30 ` Bart Van Assche
2019-04-05 4:52 ` James Bottomley
2018-10-19 4:50 Stephen Rothwell
2018-10-19 4:54 ` James Bottomley
2018-10-19 4:58 ` Stephen Rothwell
[not found] <20180620132911.5f6ab464@canb.auug.org.au>
2018-07-10 7:31 ` Stephen Rothwell
2018-07-10 14:09 ` Jens Axboe
2018-07-10 14:14 ` James Bottomley
2018-07-10 14:22 ` Jens Axboe
2018-07-10 14:26 ` James Bottomley
2018-07-10 14:35 ` Jens Axboe
2018-07-10 15:08 ` Martin K. Petersen
2018-04-17 2:25 Stephen Rothwell
2018-04-18 21:52 ` Long Li
2018-04-18 23:30 ` Martin K. Petersen
2017-04-06 4:04 Stephen Rothwell
2017-04-06 8:18 ` Fam Zheng
2016-11-22 7:44 Stephen Rothwell
2016-11-22 22:24 ` Martin K. Petersen
2016-09-13 4:15 Stephen Rothwell
2016-09-13 14:09 ` Bryant G. Ly
2016-09-15 13:55 ` Martin K. Petersen
2014-11-18 8:21 Stephen Rothwell
2014-11-20 8:23 ` Christoph Hellwig
2011-07-20 4:08 Stephen Rothwell
[not found] <20110518114912.dfdf8835.sfr@canb.auug.org.au>
2011-05-18 2:06 ` Nicholas A. Bellinger
2011-05-18 3:58 ` Stephen Rothwell
2011-05-19 2:54 ` Nicholas A. Bellinger
2011-05-19 16:18 ` Kiran Patil
2011-05-19 16:22 ` Geert Uytterhoeven
2011-06-23 17:02 ` Randy Dunlap
2010-08-04 3:13 Stephen Rothwell
2010-08-04 4:17 ` James Bottomley
2010-02-10 5:51 Stephen Rothwell
2010-02-10 22:13 ` James Bottomley
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=20130902182817.87a961aa251604b630620028@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=santoshsy@gmail.com \
--cc=sthumma@codeaurora.org \
--cc=tj@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).