linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Corey Minyard <cminyard@mvista.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the ipmi tree
Date: Tue, 16 Dec 2014 22:22:13 -0600	[thread overview]
Message-ID: <549104F5.30902@acm.org> (raw)
In-Reply-To: <20141217140353.04eebe5d@canb.auug.org.au>

On 12/16/2014 09:03 PM, Stephen Rothwell wrote:
> Hi Corey,
>
> After merging the ipmi tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/char/ipmi/ipmi_ssif.c:55:26: fatal error: linux/ctypes.h: No such file or directory
>  #include <linux/ctypes.h>
>                           ^
>
> Caused by commit 707096b4dd41 ("ipmi: Fix compile issue with isspace()").
>
> I have used the ipmi tree from next-20141216 for today.
>
> Also, you seem to have rebased your tree and thus duplicated a whole
> series of commits that are now in Linus' tree :-(

These should be fixed now.  I'm still learning the finer points of git for
this type of work.

Thanks,

-corey

  reply	other threads:[~2014-12-17  4:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-17  3:03 linux-next: build failure after merge of the ipmi tree Stephen Rothwell
2014-12-17  4:22 ` Corey Minyard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-04  1:48 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-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=549104F5.30902@acm.org \
    --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 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).