From: Maneesh Soni <maneesh@in.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: LKML <linux-kernel@vger.kernel.org>, manuel.lauss@fh-hagenberg.at
Subject: Re: Fw: 2.6.8.1-mm1: oops with firmware loading
Date: Tue, 17 Aug 2004 14:49:50 -0500 [thread overview]
Message-ID: <20040817194950.GA1536@in.ibm.com> (raw)
In-Reply-To: <20040817110533.036abf8f.akpm@osdl.org>
On Tue, Aug 17, 2004 at 11:05:33AM -0700, Andrew Morton wrote:
>
>
> Begin forwarded message:
>
> Date: Tue, 17 Aug 2004 15:28:18 +0200
> From: Manuel Lauss <manuel.lauss@fh-hagenberg.at>
> To: akpm@osdl.org, linux-kernel@vger.kernel.org
> Cc: manuel.lauss@fh-hagenberg.at
> Subject: 2.6.8.1-mm1: oops with firmware loading
>
>
> Hi,
>
> The new sysfs-backingstore patches cause an oops when I ifup a
> prism54 based device, heres the dmesg section:
>
My fault, a bad typo in fs/sysfs/bin.c.
Manuel, can you try this change in fs/sysfs/bin.c
--- bin.c.orig 2004-08-18 05:34:40.883964168 +0530
+++ bin.c 2004-08-18 05:36:40.316807616 +0530
@@ -60,8 +60,8 @@
static int
flush_write(struct dentry *dentry, char *buffer, loff_t offset, size_t count)
{
- struct bin_attribute *attr = to_bin_attr(dentry->d_parent);
- struct kobject *kobj = to_kobj(dentry);
+ struct bin_attribute *attr = to_bin_attr(dentry);
+ struct kobject *kobj = to_kobj(dentry->d_parent);
return attr->write(kobj, buffer, offset, count);
}
Andrew, How do I send the patch? I think hand editting will also work.
Thanks
Maneesh
--
Maneesh Soni
Linux Technology Center,
IBM Austin
email: maneesh@in.ibm.com
Phone: 1-512-838-1896 Fax:
T/L : 6781896
next parent reply other threads:[~2004-08-17 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040817110533.036abf8f.akpm@osdl.org>
2004-08-17 19:49 ` Maneesh Soni [this message]
2004-08-17 20:39 ` Fw: 2.6.8.1-mm1: oops with firmware loading Manuel Lauss
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=20040817194950.GA1536@in.ibm.com \
--to=maneesh@in.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manuel.lauss@fh-hagenberg.at \
/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.