linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Tomer Maimon <tmaimon77@gmail.com>
Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the spi tree
Date: Thu, 15 Nov 2018 11:26:31 -0800	[thread overview]
Message-ID: <20181115192631.GN2089@sirena.org.uk> (raw)
In-Reply-To: <CAP6Zq1gp+hmNkvk8D2uv8FUqTXE4+ZMPhMB7A7vLMaM6swHy4g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 693 bytes --]

On Thu, Nov 15, 2018 at 05:56:19PM +0200, Tomer Maimon wrote:
> Hi Mark and Stephen,
> 
> I saw the warning from the kbuilt, in this matter the ioread() function
> will call every time (and the val parameter will used) because rsize can be
> 1 or 2.
> 
> rsize = min(bytes_per_word(priv->bits_per_word), priv->rx_bytes);
> bytes_per_word(priv->bits_per_word)function return 1 or 2.
> npcm_pspi_recv()function will called only if parameter priv->rx_bytes is
> not 0.
> 
> please let me know if you think that I still need to modify the npcm_pspi_recv
> to fix kbuilt warning.

Please, it's going to create noise for people working on the kernel if
they get a spurious warning.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2018-11-15 19:26 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-14  2:18 linux-next: build warning after merge of the spi tree Stephen Rothwell
     [not found] ` <CAP6Zq1gp+hmNkvk8D2uv8FUqTXE4+ZMPhMB7A7vLMaM6swHy4g@mail.gmail.com>
2018-11-15 19:26   ` Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-07  6:31 Stephen Rothwell
2024-05-07 13:16 ` Andy Shevchenko
2024-02-16  3:11 Stephen Rothwell
2024-02-19 11:18 ` Dhruva Gole
2024-02-08  3:52 Stephen Rothwell
2024-02-08 11:43 ` Mark Brown
2024-02-08 13:32 ` Amadeusz Sławiński
2024-02-08 21:59   ` Stephen Rothwell
2022-06-08  4:30 Stephen Rothwell
2022-06-08  7:30 ` David Jander
2022-06-08 10:05   ` Mark Brown
2021-08-10  6:29 Stephen Rothwell
2021-08-09  5:30 Stephen Rothwell
2021-04-20  3:48 Stephen Rothwell
2021-04-20  7:56 ` Patrice CHOTARD
2021-04-06  6:48 Stephen Rothwell
2021-04-06  7:38 ` Jay Fang
2021-01-11  1:09 Stephen Rothwell
2021-01-04  0:06 Stephen Rothwell
2021-01-04  7:56 ` Ardelean, Alexandru
2020-07-09  4:10 Stephen Rothwell
2020-07-09  5:29 ` Peng Fan
2020-04-28  4:16 Stephen Rothwell
2020-04-28  5:01 ` Sanjay R Mehta
2020-04-28  9:38   ` Mark Brown
2020-01-15  2:23 Stephen Rothwell
2020-01-15  9:10 ` Jean Pihet
2020-01-15 10:27   ` Stephen Rothwell
2020-01-15 11:38     ` Jean Pihet
2019-04-29  4:30 Stephen Rothwell
2019-01-29  2:02 Stephen Rothwell
2019-01-29  6:57 ` Yogesh Narayan Gaur
2019-01-29  7:25   ` Schrempf Frieder
2019-01-29  8:26   ` Stephen Rothwell
2019-01-29  8:39     ` Yogesh Narayan Gaur
2019-01-10  0:44 Stephen Rothwell
2019-01-10  0:41 Stephen Rothwell
2018-08-03  4:37 Stephen Rothwell
2017-03-27  2:41 Stephen Rothwell
2017-03-27  5:33 ` Vignesh R
2010-10-14  1:59 Stephen Rothwell
2010-10-14  5:00 ` Grant Likely

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=20181115192631.GN2089@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tmaimon77@gmail.com \
    /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).