linux-kernel - Re: linux-next: build warning after merge of the scsi tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 04 Sep 2013 15:24:27 +0530
From:	Sujit Reddy Thumma <sthumma@...eaurora.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	James Bottomley <James.Bottomley@...senPartnership.com>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Santosh Y <santoshsy@...il.com>, Tejun Heo <tj@...nel.org>
Subject: Re: linux-next: build warning after merge of the scsi tree

On 9/4/2013 2:48 PM, Sujit Reddy Thumma wrote:
> On 9/2/2013 1:58 PM, Stephen Rothwell wrote:
>> 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);
>>     ^
>
> James, would you like to pick up follow-up patch @
> http://marc.info/?l=linux-scsi&m=137819519527432&w=2
> or let me update the commit c1e846ab4422 fixing this?

Ignore this.
I saw you have dropped the patchset already. I will fix and post the
updated patches soon. Thanks.

>
>>
>> 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.
>>
>

-- 
Regards,
Sujit
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/