linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Corey Minyard <cminyard@mvista.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: build failure after merge of the ipmi tree
Date: Mon, 17 Nov 2014 19:20:09 +1100	[thread overview]
Message-ID: <20141117192009.735e8b6b@canb.auug.org.au> (raw)

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

Hi Corey,

After merging the ipmi tree, today's linux-next build (powerpc
allyesconfig) failed like this:


drivers/char/ipmi/ipmi_ssif.c: In function 'ssif_probe':
drivers/char/ipmi/ipmi_ssif.c:1377:23: error: 'union ipmi_smi_info_union' has no member named 'acpi_info'
   ssif_info->addr_info.acpi_info.acpi_handle = acpi_handle;
                       ^

Caused by commit 66a4d9633da8 ("ipmi: Add SMBus interface driver (SSIF)").

I have reverted that commit (and the following 1c99788eebd9 "ipmi:
Handle I2C parms in the SSIF driver") for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2014-11-17  8:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-17  8:20 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-04  1:48 linux-next: build failure after merge of the ipmi tree Stephen Rothwell
2022-11-04  2:14 ` Corey Minyard
2021-10-01  2:52 Stephen Rothwell
2021-10-01 12:15 ` 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: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=20141117192009.735e8b6b@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=cminyard@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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 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).