From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Andrew Morton <akpm@osdl.org>
Cc: adobriyan@gmail.com, spyro@f2s.com, domen@coderock.org,
linux-kernel@vger.kernel.org, philb@gnu.org
Subject: Re: [PATCH] Remove drivers/parport/parport_arc.c
Date: Wed, 14 Sep 2005 22:29:39 +0100 [thread overview]
Message-ID: <20050914222938.E30746@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20050914141631.1567758b.akpm@osdl.org>; from akpm@osdl.org on Wed, Sep 14, 2005 at 02:16:31PM -0700
On Wed, Sep 14, 2005 at 02:16:31PM -0700, Andrew Morton wrote:
> Russell King <rmk+lkml@arm.linux.org.uk> wrote:
> >
> > On Thu, Sep 15, 2005 at 12:24:20AM +0400, Alexey Dobriyan wrote:
> > > From: Domen Puncer <domen@coderock.org>
> > >
> > > Remove nowhere referenced file (grep "parport_arc\." didn't find anything).
> >
> > Maybe Ian Molton might like to ensure that this is linked in to the
> > build.
> >
>
> Yeah, except it's also unused in 2.4 and includes non-existent header
> files. Probably it's an ex-parrot but it'd be worth an attempt to get
> it to compile before we remove it.
True - I never had a machine which parport_arc was used on, so it
existed from the time when parport was initially written and remained
in that rather sad state. The only person I know who may have tinkered
with it would be Dave Gilbert.
However, it's now within the set of machines which Ian looks after, so
Ian should at least know of its impending demise.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-09-14 21:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 20:24 [PATCH] Remove drivers/parport/parport_arc.c Alexey Dobriyan
2005-09-14 21:08 ` Russell King
2005-09-14 21:16 ` Andrew Morton
2005-09-14 21:29 ` Russell King [this message]
2005-09-14 21:42 ` Ian Molton
2005-09-14 22:24 ` Phil Blundell
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=20050914222938.E30746@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--cc=domen@coderock.org \
--cc=linux-kernel@vger.kernel.org \
--cc=philb@gnu.org \
--cc=spyro@f2s.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 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.