public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
	David Woodhouse <David.Woodhouse@intel•com>,
	akpm <akpm@linux-foundation•org>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
	KOSAKI Motohiro <kosaki.motohiro@jp•fujitsu.com>,
	Simon Kagstrom <simon.kagstrom@netinsight•net>
Subject: [PATCH -next -resend] kmsg_dump.h: needs errno.h
Date: Wed, 1 Jun 2011 09:14:03 -0700	[thread overview]
Message-ID: <20110601091403.1e41ef91.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110601134322.f59f5603.sfr@canb.auug.org.au>

From: Randy Dunlap <randy.dunlap@oracle•com>

Fix <linux/kmsg_dump.h> when CONFIG_PRINTK is not enabled:

include/linux/kmsg_dump.h:56: error: 'EINVAL' undeclared (first use in this function)
include/linux/kmsg_dump.h:61: error: 'EINVAL' undeclared (first use in this function)

Looks like previous commit:
commit 595dd3d8bf953254d8d2f30f99c54fe09c470040
Author: Randy Dunlap <randy.dunlap@oracle•com>
Date:   Tue Dec 1 10:52:02 2009 -0800

    kmsg_dump: fix build for CONFIG_PRINTK=n

uses EINVAL without having the needed header file(s),
but I'm sure that I build tested that patch also.  oh well.

Signed-off-by: Randy Dunlap <randy.dunlap@oracle•com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp•fujitsu.com>
Cc: Simon Kagstrom <simon.kagstrom@netinsight•net>
Cc: David Woodhouse <David.Woodhouse@intel•com>
---
 include/linux/kmsg_dump.h |    1 +
 1 file changed, 1 insertion(+)

--- linux-next-20110524.orig/include/linux/kmsg_dump.h
+++ linux-next-20110524/include/linux/kmsg_dump.h
@@ -12,6 +12,7 @@
 #ifndef _LINUX_KMSG_DUMP_H
 #define _LINUX_KMSG_DUMP_H
 
+#include <linux/errno.h>
 #include <linux/list.h>
 
 enum kmsg_dump_reason {

      reply	other threads:[~2011-06-01 16:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01  3:43 linux-next: Tree for June 1 Stephen Rothwell
2011-06-01 16:14 ` Randy Dunlap [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=20110601091403.1e41ef91.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle$(echo .)com \
    --cc=David.Woodhouse@intel$(echo .)com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=kosaki.motohiro@jp$(echo .)fujitsu.com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=simon.kagstrom@netinsight$(echo .)net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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