From: akpm@linux-foundation.org
To: randy.dunlap@oracle.com, david-b@pacbell.net,
dsilvers@simtec.co.uk, ext-jani.1.nikula@nokia.com,
mm-commits@vger.kernel.org
Subject: [folded] gpiolib-allow-exported-gpio-nodes-to-be-named-using-sysfs-links-update-fix.patch removed from -mm tree
Date: Tue, 22 Sep 2009 14:49:18 -0700 [thread overview]
Message-ID: <200909222149.n8MLnIsC012155@imap1.linux-foundation.org> (raw)
The patch titled
gpio.h: fix warning for GENERIC_GPIO=n
has been removed from the -mm tree. Its filename was
gpiolib-allow-exported-gpio-nodes-to-be-named-using-sysfs-links-update-fix.patch
This patch was dropped because it was folded into gpiolib-allow-exported-gpio-nodes-to-be-named-using-sysfs-links.patch
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: gpio.h: fix warning for GENERIC_GPIO=n
From: Randy Dunlap <randy.dunlap@oracle.com>
Fix build for CONFIG_GENERIC_GPIO=n, which causes this warning:
include/linux/gpio.h:93: warning: 'struct device' declared inside parameter list
include/linux/gpio.h:93: warning: its scope is only this definition or declaration, which is probably not what you want
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Jani Nikula <ext-jani.1.nikula@nokia.com>
Cc: David Brownell <david-b@pacbell.net>
Cc: Daniel Silverstone <dsilvers@simtec.co.uk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/gpio.h | 2 ++
1 file changed, 2 insertions(+)
diff -puN include/linux/gpio.h~gpiolib-allow-exported-gpio-nodes-to-be-named-using-sysfs-links-update-fix include/linux/gpio.h
--- a/include/linux/gpio.h~gpiolib-allow-exported-gpio-nodes-to-be-named-using-sysfs-links-update-fix
+++ a/include/linux/gpio.h
@@ -12,6 +12,8 @@
#include <linux/types.h>
#include <linux/errno.h>
+struct device;
+
/*
* Some platforms don't support the GPIO programming interface.
*
_
Patches currently in -mm which might be from randy.dunlap@oracle.com are
origin.patch
procfs-provide-stack-information-for-threads-v08.patch
kcore-register-vmemmap-range.patch
spih-add-missing-kernel-doc-for-struct-spi_master.patch
gpiolib-allow-exported-gpio-nodes-to-be-named-using-sysfs-links.patch
gpiolib-allow-exported-gpio-nodes-to-be-named-using-sysfs-links-update-fix.patch
reply other threads:[~2009-09-22 21:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200909222149.n8MLnIsC012155@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=dsilvers@simtec.co.uk \
--cc=ext-jani.1.nikula@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=randy.dunlap@oracle.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 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.