mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jocelyn Falempe <jfalempe@redhat.com>
To: Venkat Rao Bagalkote <venkat88@linux.vnet.ibm.com>,
	akpm@linux-foundation.org, naveen.n.rao@linux.ibm.com,
	mpe@ellerman.id.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: [linux-next-20240626]Kernel Build Fails on repo linux-next-20240626
Date: Thu, 27 Jun 2024 11:33:50 +0200	[thread overview]
Message-ID: <fa16b034-5511-4db7-aa83-9ece8bc07c89@redhat.com> (raw)
In-Reply-To: <32f20573-7e3b-496a-8c02-9234d410113e@linux.vnet.ibm.com>

Hi,

I think this patch was merged by mistake, as it was not yet reviewed. 
can someone revert it ?

-- 

Jocelyn

On 27/06/2024 06:21, Venkat Rao Bagalkote wrote:
> Greetings!!!
> 
> 
> Kernel Build fails with below error, while building with 
> linux-next(next-20240626) repo.
> 
> 
> arch/powerpc/kernel/nvram_64.c:79:17: error: initialization of ‘void 
> (*)(struct kmsg_dumper *, enum kmsg_dump_reason,  const char *)’ from 
> incompatible pointer type ‘void (*)(struct kmsg_dumper *, enum 
> kmsg_dump_reason)’ [-Werror=incompatible-pointer-types]
>     79 |         .dump = oops_to_nvram
>        |                 ^~~~~~~~~~~~~
> arch/powerpc/kernel/nvram_64.c:79:17: note: (near initialization for 
> ‘nvram_kmsg_dumper.dump’)
> arch/powerpc/kernel/nvram_64.c:645:13: error: conflicting types for 
> ‘oops_to_nvram’; have ‘void(struct kmsg_dumper *, enum 
> kmsg_dump_reason,  const char *)’
>    645 | static void oops_to_nvram(struct kmsg_dumper *dumper,
>        |             ^~~~~~~~~~~~~
> arch/powerpc/kernel/nvram_64.c:75:13: note: previous declaration of 
> ‘oops_to_nvram’ with type ‘void(struct kmsg_dumper *, enum 
> kmsg_dump_reason)’
>     75 | static void oops_to_nvram(struct kmsg_dumper *dumper,
>        |             ^~~~~~~~~~~~~
> arch/powerpc/kernel/nvram_64.c:75:13: error: ‘oops_to_nvram’ used but 
> never defined [-Werror]
> arch/powerpc/kernel/nvram_64.c:645:13: error: ‘oops_to_nvram’ defined 
> but not used [-Werror=unused-function]
>    645 | static void oops_to_nvram(struct kmsg_dumper *dumper,
>        |             ^~~~~~~~~~~~~
> cc1: all warnings being treated as errors
> make[4]: *** [scripts/Makefile.build:244: 
> arch/powerpc/kernel/nvram_64.o] Error 1
> make[4]: *** Waiting for unfinished jobs....
> make[3]: *** [scripts/Makefile.build:485: arch/powerpc/kernel] Error 2
> 
> make[2]: *** [scripts/Makefile.build:485: arch/powerpc] Error 2
> 
> 
> This issue has been introduced with the below commit.
> 
> 
> Commit ID: 7e72bb7504d1192ab89809f6192dba1b06f4fa51.
> 
> 
> Regards,
> 
> Venkat.
> 


      reply	other threads:[~2024-06-27  9:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-27  4:21 Venkat Rao Bagalkote
2024-06-27  9:33 ` Jocelyn Falempe [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=fa16b034-5511-4db7-aa83-9ece8bc07c89@redhat.com \
    --to=jfalempe@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=naveen.n.rao@linux.ibm.com \
    --cc=venkat88@linux.vnet.ibm.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

all inboxes | Powered by JetHome®