All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Corey Minyard <cminyard@mvista.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 ipmi tree
Date: Fri, 1 Oct 2021 07:15:21 -0500	[thread overview]
Message-ID: <20211001121521.GP5419@minyard.net> (raw)
In-Reply-To: <20211001125248.30adbdf3@canb.auug.org.au>

On Fri, Oct 01, 2021 at 12:52:48PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the ipmi tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> drivers/char/ipmi/ipmi_msghandler.c: In function 'bmc_device_id_handler':
> drivers/char/ipmi/ipmi_msghandler.c:2376:3: error: label 'out' used but not defined
>  2376 |   goto out;
>       |   ^~~~

I botched a cherry pick, it should be fixed now.  Sorry about that.

Thanks for the work you do.

-corey

> 
> Caused by commit
> 
>   2d7a6d8467f9 ("ipmi: Check error code before processing BMC response")
> 
> I have used the ipmi tree from next-20210930 for today.
> 
> -- 
> Cheers,
> Stephen Rothwell



  reply	other threads:[~2021-10-01 12:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01  2:52 linux-next: build failure after merge of the ipmi tree Stephen Rothwell
2021-10-01 12:15 ` Corey Minyard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-04-03 14:01 Mark Brown
2026-04-03 15:41 ` Corey Minyard
2022-11-04  1:48 Stephen Rothwell
2022-11-04  2:14 ` Corey Minyard
2020-04-20  3:09 Stephen Rothwell
2020-04-20  3:51 ` Feng Tang
2019-04-03  3:33 Stephen Rothwell
2019-04-03 20:27 ` Corey Minyard
2019-04-03 21:12   ` Corey Minyard
2019-04-04  0:14     ` Paul E. McKenney
2017-09-28  4:45 Stephen Rothwell
2017-09-28 17:34 ` Corey Minyard
2014-12-17  3:03 Stephen Rothwell
2014-12-17  4:22 ` Corey Minyard
2014-11-17  8:20 Stephen Rothwell
2014-11-17  8:14 Stephen Rothwell

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=20211001121521.GP5419@minyard.net \
    --to=minyard@acm.org \
    --cc=cminyard@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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 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.