From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the libata tree
Date: Mon, 20 Jun 2022 23:07:40 +0300 [thread overview]
Message-ID: <54db2644-aa04-82cc-88cd-1cb40a2b2d77@omp.ru> (raw)
In-Reply-To: <71cca7ed-6409-3066-8878-cdc647b17057@opensource.wdc.com>
On 6/20/22 2:07 PM, Damien Le Moal wrote:
[...]
>>>>> After merging the libata tree, today's linux-next build (powercp
>>>>> ppc64_defconfig) produced this warning:
>>>>>
>>>>> In file included from include/linux/device.h:15,
>>>>> from arch/powerpc/include/asm/io.h:27,
>>>>> from include/linux/io.h:13,
>>>>> from include/linux/irq.h:20,
>>>>> from arch/powerpc/include/asm/hardirq.h:6,
>>>>> from include/linux/hardirq.h:11,
>>>>> from include/linux/highmem.h:11,
>>>>> from include/linux/bvec.h:10,
>>>>> from include/linux/blk_types.h:10,
>>>>> from include/linux/blkdev.h:9,
>>>>> from drivers/ata/pata_macio.c:18:
>>>>> drivers/ata/pata_macio.c: In function 'pmac_macio_calc_timing_masks':
>>>>> drivers/ata/pata_macio.c:1031:28: warning: format '%lx' expects argument of type 'long unsigned int', but argument 4 has type 'unsigned int' [-Wformat=]
>>>>> 1031 | dev_dbg(priv->dev, "Supported masks: PIO=%lx, MWDMA=%lx, UDMA=%lx\n",
>>>>
>>>> .
>>>> .
>>>> .
>>>>
>>>>> Introduced by commit
>>>>>
>>>>> f0a6d77b351c ("ata: make transfer mode masks *unsigned int*")
>>
>> Oops, sorry about that!>
>>>> This turned into a build failure in my powerpc allyesconfig build, so I
>>>> reverted the above commit for today.
>>>
>>> I pushed the fix already. It is in ata for-next branch.
>>
>> Thank you!
>> Note that your Fixes: tag doesn't look right -- the asterisks are missing
>> in the summary...
>
> Fixed. Copy-paste from the mailer (build failure report email), the
> asterisks are gone and "unsigned int" shown with bold font. Please stop
Strange, I'm seeing both asterisks and bold font there. What kind of MUA
you use? :-)
> with the markdown style emphasis. That creates problems.
Mhm, OK...
MBR, Sergey
next prev parent reply other threads:[~2022-06-20 20:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 0:34 linux-next: build warning after merge of the libata tree 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 [this message]
2022-06-20 20:08 ` Sergey Shtylyov
-- strict thread matches above, loose matches on Subject: below --
2022-09-19 2:40 Stephen Rothwell
2022-09-19 8:01 ` Damien Le Moal
2022-09-19 23:56 ` Damien Le Moal
2022-09-20 19:25 ` Serge Semin
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=54db2644-aa04-82cc-88cd-1cb40a2b2d77@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=damien.lemoal@opensource.wdc.com \
--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).