From: Wolfram Sang <wsa-dev@sang-engineering.com>
To: Dan Carpenter <error27@gmail.com>
Cc: oe-kbuild@lists.linux.dev, lkp@intel.com,
oe-kbuild-all@lists.linux.dev,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [linux-next:master 8444/9537] drivers/mmc/host/renesas_sdhi_internal_dmac.c:327 renesas_sdhi_internal_dmac_dma_irq() warn: set_bit() takes a bit number
Date: Tue, 22 Nov 2022 09:42:34 +0100 [thread overview]
Message-ID: <Y3yLerDI33CAgEUe@ninjato> (raw)
In-Reply-To: <Y3yETLzmBhjVeOr/@kadam>
[-- Attachment #1: Type: text/plain, Size: 155 bytes --]
> These warnings are normally harmless because people write consistent
Yes, the code still works. Using APIs not correctly doesn't look good,
though...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-11-22 8:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 20:18 [linux-next:master 8444/9537] drivers/mmc/host/renesas_sdhi_internal_dmac.c:327 renesas_sdhi_internal_dmac_dma_irq() warn: set_bit() takes a bit number kernel test robot
2022-11-22 7:10 ` Dan Carpenter
2022-11-22 7:16 ` Wolfram Sang
2022-11-22 8:11 ` Dan Carpenter
2022-11-22 8:42 ` Wolfram Sang [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=Y3yLerDI33CAgEUe@ninjato \
--to=wsa-dev@sang-engineering.com \
--cc=error27@gmail.com \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oe-kbuild@lists.linux.dev \
--cc=ulf.hansson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.