From: Mark Brown <broonie@kernel.org>
To: linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
Alexandru Ardelean <alexandru.ardelean@analog.com>
Cc: andy.shevchenko@gmail.com, sfr@canb.auug.org.au
Subject: Re: [PATCH v2] spi: stm32: update dev_dbg() print format for SPI params
Date: Tue, 05 Jan 2021 16:08:10 +0000 [thread overview]
Message-ID: <160986289006.50207.10241683421352392982.b4-ty@kernel.org> (raw)
In-Reply-To: <20210104143103.56510-1-alexandru.ardelean@analog.com>
On Mon, 4 Jan 2021 16:31:03 +0200, Alexandru Ardelean wrote:
> With the introduction of the 'include/uapi/linux/spi/spi.h' header, the
> type of the macros are enforced to 'unsigned long int' via the _BITUL()
> macro.
>
> This causes some -Wformat warnings in the spi-stm32 driver.
> This patch adds a double-negation operator to the bit-masks. Essentially,
> the important values for debugging are 0 or 1, while masking them directly
> would show 0 or BIT(x) values.
> This way, the type of the arguments are automatically re-cast.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: stm32: update dev_dbg() print format for SPI params
commit: 8b835da61774d4482864bc081dfb428104842ad3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
next prev parent reply other threads:[~2021-01-05 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 8:59 [PATCH] " Alexandru Ardelean
2021-01-04 13:50 ` Andy Shevchenko
2021-01-04 14:13 ` Ardelean, Alexandru
2021-01-04 14:31 ` [PATCH v2] " Alexandru Ardelean
2021-01-04 14:42 ` Andy Shevchenko
2021-01-05 16:08 ` Mark Brown [this message]
2021-01-05 16:08 ` [PATCH] " Mark Brown
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=160986289006.50207.10241683421352392982.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alexandru.ardelean@analog.com \
--cc=andy.shevchenko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@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
all inboxes | Powered by JetHome®