From: Stian Jordet <liste@jordet.nu>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: usbfs mount options doesn't work in 2.6, works fine with 2.4
Date: Wed, 10 Dec 2003 23:04:07 +0100 [thread overview]
Message-ID: <1071093847.10327.0.camel@chevrolet.hybel> (raw)
In-Reply-To: <20031210213142.GB8784@kroah.com>
ons, 10.12.2003 kl. 22.31 skrev Greg KH:
> On Mon, Dec 08, 2003 at 05:59:10AM +0100, Stian Jordet wrote:
> > man, 08.12.2003 kl. 05.52 skrev Stian Jordet:
> > > Is this something other people are
> > > experiencing as well, or is this some kind of configuration problem? I'm
> Yeah, it's a bug. I haven't had the time to track it down yet. Any
> help with this would be greatly appreciated.
I'd be happy to help, if I weren't too stupid with C. Sorry :(
Best regards,
Stian
next prev parent reply other threads:[~2003-12-10 22:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 4:52 usbfs mount options doesn't work in 2.6, works fine with 2.4 Stian Jordet
2003-12-08 4:59 ` Stian Jordet
2003-12-10 21:31 ` Greg KH
2003-12-10 22:04 ` Stian Jordet [this message]
2003-12-11 9:07 ` Duncan Sands
2003-12-11 14:47 ` OGAWA Hirofumi
2003-12-11 15:03 ` OGAWA Hirofumi
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=1071093847.10327.0.camel@chevrolet.hybel \
--to=liste@jordet.nu \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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).