From: Mike Murphy <mamurph@cs.clemson.edu>
To: Greg KH <greg@kroah.com>
Cc: Oliver Neukum <oliver@neukum.org>,
linux-usb@vger.kernel.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] input: xpad.c - Xbox 360 wireless and sysfs support
Date: Tue, 17 Feb 2009 13:27:48 -0500 [thread overview]
Message-ID: <5aa163d00902171027o139ba751r8103f948f3f492bb@mail.gmail.com> (raw)
In-Reply-To: <5aa163d00902162057l106c001bo519a5241c79b5e96@mail.gmail.com>
On Mon, Feb 16, 2009 at 11:57 PM, Mike Murphy <mamurph@cs.clemson.edu> wrote:
> Unless that is some common error that is obvious from its description,
> I will have to chase the bug down tomorrow or Wednesday. It's getting
> a bit late here.
>
Fixed... the function signature was wrong. Should have been:
static ssize_t xpad_show_dead_zone(struct device *dev, struct
device_attribute *attr, char *buf)
Incidentally, both Documentation/driver-model/device.txt and
Documentation/filesystems/sysfs.txt appear to be wrong. The former
defines the device attribute structure as:
struct device_attribute {
struct attribute attr;
ssize_t (*show)(struct device * dev, char * buf, size_t count,
loff_t off);
ssize_t (*store)(struct device * dev, const char * buf, size_t
count, loff_t off);
};
while the latter (that I followed last night) defines it as:
struct device_attribute {
struct attribute attr;
ssize_t (*show)(struct device * dev, char * buf);
ssize_t (*store)(struct device * dev, const char * buf);
};
I finally got the correct one out of include/linux/device.h:
struct device_attribute {
struct attribute attr;
ssize_t (*show)(struct device *dev, struct device_attribute *attr,
char *buf);
ssize_t (*store)(struct device *dev, struct device_attribute *attr,
const char *buf, size_t count);
};
Thanks,
Mike
--
Mike Murphy
Ph.D. Candidate and NSF Graduate Research Fellow
Clemson University School of Computing
120 McAdams Hall
Clemson, SC 29634-0974 USA
Tel: +1 864.656.2838 Fax: +1 864.656.0145
http://cirg.cs.clemson.edu/~mamurph
next prev parent reply other threads:[~2009-02-17 18:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5aa163d00902142008g138826br80d3ea989e7af691@mail.gmail.com>
2009-02-16 8:31 ` [PATCH] input: xpad.c - Xbox 360 wireless and sysfs support Oliver Neukum
[not found] ` <200902160931.34771.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2009-02-16 13:22 ` Mike Murphy
[not found] ` <5aa163d00902160522r3a22412je3f5202076f57a0a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-02-16 15:21 ` Oliver Neukum
2009-02-19 4:04 ` Mike Murphy
2009-02-16 16:13 ` Greg KH
2009-02-16 18:09 ` Mike Murphy
[not found] ` <5aa163d00902161009l15dae120le96436d40f998d33-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-02-16 18:59 ` Greg KH
[not found] ` <20090216185914.GA6239-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2009-02-16 19:30 ` Mike Murphy
2009-02-16 20:22 ` Greg KH
2009-02-17 2:53 ` Mike Murphy
2009-02-17 3:18 ` Greg KH
2009-02-17 4:57 ` Mike Murphy
2009-02-17 18:27 ` Mike Murphy [this message]
[not found] ` <5aa163d00902171027o139ba751r8103f948f3f492bb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-02-17 18:39 ` Greg KH
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=5aa163d00902171027o139ba751r8103f948f3f492bb@mail.gmail.com \
--to=mamurph@cs.clemson.edu \
--cc=greg@kroah.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.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).