From: "dave" <davekern@ihug.co.nz>
To: "Tomas Szepe" <szepe@pinerecords.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Help writing FS and proc
Date: Tue, 8 Apr 2003 22:21:57 -0700 [thread overview]
Message-ID: <003301c2fe57$f2f4e220$0b721cac@stacy> (raw)
In-Reply-To: 20030407210208.GE3446@louise.pinerecords.com
----- Original Message -----
From: "Tomas Szepe" <szepe@pinerecords.com>
To: "dave" <davekern@ihug.co.nz>
Cc: <linux-kernel@vger.kernel.org>
Sent: Monday, April 07, 2003 2:02 PM
Subject: Re: Help writing FS and proc
> > RELASE
> > REALISE
>
> Third time's the charm?
>
Will thank you I will now have a driver that is not completed but the
spelling is correct :)
prev parent reply other threads:[~2003-04-08 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 7:57 Help writing FS and proc dave
2003-04-07 21:02 ` Tomas Szepe
2003-04-09 5:21 ` dave [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='003301c2fe57$f2f4e220$0b721cac@stacy' \
--to=davekern@ihug.co.nz \
--cc=linux-kernel@vger.kernel.org \
--cc=szepe@pinerecords.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox