From: Adrian Bunk <bunk@stusta.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
torvalds@osdl.org
Subject: Re: [PATCH] small ftape cleanups
Date: Sun, 9 Jan 2005 03:05:56 +0100 [thread overview]
Message-ID: <20050109020556.GM14108@stusta.de> (raw)
In-Reply-To: <1105231821.12004.19.camel@localhost.localdomain>
On Sun, Jan 09, 2005 at 12:50:22AM +0000, Alan Cox wrote:
> The changeset below was submitted with the wrong documentation. Any
> chance of someone providing the right documentation to the actual large
> change to ftape below (which does look sane but nothign to do with rio)
s/rio/ftape/ and the description is correct.
> > ChangeSet 1.2406, 2005/01/08 14:19:45-08:00, bunk@stusta.de
> >
> > [PATCH] small ftape cleanups
> >
> > The patch below does cleanups under drivers/char/rio/ including the
> > following:
> >
> > - remove some completely unused code
> > - make some needlessly global code static
> >
> > Signed-off-by: Adrian Bunk <bunk@stusta.de>
> > Signed-off-by: Andrew Morton <akpm@osdl.org>
> > Signed-off-by: Linus Torvalds <torvalds@osdl.org>
> >
> >
> >
> > compressor/zftape-compress.c | 4 --
> > lowlevel/fc-10.c | 4 +-
> > lowlevel/fdc-io.c | 67 ++++++-------------------------------------
> > lowlevel/fdc-io.h | 5 ---
> > lowlevel/ftape-bsm.c | 8 ++++-
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2005-01-09 2:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200501082336.j08Na0ha003117@hera.kernel.org>
2005-01-09 0:50 ` [PATCH] small ftape cleanups Alan Cox
2005-01-09 2:05 ` Adrian Bunk [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=20050109020556.GM14108@stusta.de \
--to=bunk@stusta.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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).