All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christian Schoenebeck <linux_oss@crudebyte.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the v9fs tree
Date: Mon, 5 Dec 2022 13:10:18 +0900	[thread overview]
Message-ID: <Y41vKkaH9tvRXCfv@codewreck.org> (raw)
In-Reply-To: <20221205150316.6fac25f2@canb.auug.org.au>

Stephen Rothwell wrote on Mon, Dec 05, 2022 at 03:03:16PM +1100:
> After merging the v9fs tree, today's linux-next build (i386 defconfig)
> failed like this:
> 
> In file included from include/linux/kernel.h:29,
>                  from arch/x86/include/asm/percpu.h:27,
>                  from arch/x86/include/asm/nospec-branch.h:14,
>                  from arch/x86/include/asm/paravirt_types.h:27,
>                  from arch/x86/include/asm/ptrace.h:97,
>                  from arch/x86/include/asm/math_emu.h:5,
>                  from arch/x86/include/asm/processor.h:13,
>                  from arch/x86/include/asm/timex.h:5,
>                  from include/linux/timex.h:67,
>                  from include/linux/time32.h:13,
>                  from include/linux/time.h:60,
>                  from include/linux/stat.h:19,
>                  from include/linux/module.h:13,
>                  from net/9p/client.c:11:
> net/9p/client.c: In function 'p9_check_errors':
> include/linux/kern_levels.h:5:25: error: format '%ld' expects argument of type 'long int', but argument 3 has type 'size_t' {aka 'unsigned int'} [-Werror=format=]
>     5 | #define KERN_SOH        "\001"          /* ASCII Start Of Header */
>       |                         ^~~~~~
> include/linux/printk.h:429:25: note: in definition of macro 'printk_index_wrap'
>   429 |                 _p_func(_fmt, ##__VA_ARGS__);                           \
>       |                         ^~~~
> include/linux/printk.h:500:9: note: in expansion of macro 'printk'
>   500 |         printk(KERN_ERR pr_fmt(fmt), ##__VA_ARGS__)
>       |         ^~~~~~
> include/linux/kern_levels.h:11:25: note: in expansion of macro 'KERN_SOH'
>    11 | #define KERN_ERR        KERN_SOH "3"    /* error conditions */
>       |                         ^~~~~~~~
> include/linux/printk.h:500:16: note: in expansion of macro 'KERN_ERR'
>   500 |         printk(KERN_ERR pr_fmt(fmt), ##__VA_ARGS__)
>       |                ^~~~~~~~
> net/9p/client.c:523:17: note: in expansion of macro 'pr_err'
>   523 |                 pr_err(
>       |                 ^~~~~~
> cc1: all warnings being treated as errors
> 
> Caused by commit
> 
>   36cd2f80abf8 ("net/9p: fix response size check in p9_check_errors()")
> 
> I have applied the following patch for today:

Thank you!
I guess I should start building one 32bit kernel somewhere...

I've amended the bad commit with this and added a note to the patch
thanking you (not quite sure how to express that with xx-by: like tags,
it's just words -- if you care and have a suggestion feel free)

-- 
Dominique

  reply	other threads:[~2022-12-05  4:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-05  4:03 linux-next: build failure after merge of the v9fs tree Stephen Rothwell
2022-12-05  4:10 ` Dominique Martinet [this message]
2022-12-05  4:55   ` Stephen Rothwell
2022-12-05 14:31   ` Christian Schoenebeck
2022-12-05 20:40     ` Christian Schoenebeck
2022-12-05 22:41       ` Dominique Martinet
2022-12-08 15:55         ` Christian Schoenebeck
2022-12-08 23:53           ` Dominique Martinet
2022-12-09 14:40             ` Christian Schoenebeck
2022-12-09 21:24               ` Dominique Martinet
  -- strict thread matches above, loose matches on Subject: below --
2022-07-13  1:02 Stephen Rothwell
2022-07-13  1:06 ` Dominique Martinet
2011-12-01  1:02 Stephen Rothwell
2011-12-01 16:57 ` Joe Perches
2011-02-22  0:53 Stephen Rothwell
2011-02-22  5:20 ` Venkateswararao Jujjuri (JV)
2011-02-22  5:30   ` Stephen Rothwell
2011-02-22  6:22     ` Venkateswararao Jujjuri (JV)
2011-02-22 14:57       ` Eric Van Hensbergen
2011-02-22 16:48         ` Venkateswararao Jujjuri (JV)

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=Y41vKkaH9tvRXCfv@codewreck.org \
    --to=asmadeus@codewreck.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux_oss@crudebyte.com \
    --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 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.