From: Kalle Valo <kvalo@codeaurora.org>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
linux-next@vger.kernel.org, sfr@canb.auug.org.au,
Stanislaw Gruszka <stf_xl@wp.pl>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] iwlwifi: fix build warnings with format string
Date: Fri, 10 Jan 2020 15:16:18 +0200 [thread overview]
Message-ID: <87muavsb8d.fsf@codeaurora.org> (raw)
In-Reply-To: <1578322389-13716-1-git-send-email-akinobu.mita@gmail.com> (Akinobu Mita's message of "Mon, 6 Jan 2020 23:53:09 +0900")
(please cc linux-wireless on all wireless patches)
Akinobu Mita <akinobu.mita@gmail.com> writes:
> This fixes build warnings introduced by commit "iwlegacy: use
> <linux/units.h> helpers" (iwlegacy-use-linux-unitsh-helpers.patch in -mm)
>
> The format '%d' has to be changed to '%ld' because the return type of
> kelvin_to_celsius() is 'long'.
>
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Link: https://lore.kernel.org/r/20200106171452.201c3b4c@canb.auug.org.au
> Cc: Kalle Valo <kvalo@codeaurora.org>
> Cc: Stanislaw Gruszka <stf_xl@wp.pl>
> Signed-off-by: Akinobu Mita <akinobu.mita@gmail.com>
I don't know what's Andrew's workflow, but shouldn't the original patch
be fixed instead?
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2020-01-10 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 6:14 linux-next: build warnings after merge of the akpm-current tree Stephen Rothwell
2020-01-06 14:53 ` [PATCH] iwlwifi: fix build warnings with format string Akinobu Mita
2020-01-10 13:16 ` Kalle Valo [this message]
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=87muavsb8d.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=stf_xl@wp.pl \
/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).