All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Molton <spyro@f2s.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
	adobriyan@gmail.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:42:10 +0100	[thread overview]
Message-ID: <43289932.7090604@f2s.com> (raw)
In-Reply-To: <20050914141631.1567758b.akpm@osdl.org>

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.

Well unless the parport stuff changed to support ports where one cant 
read the data latch, its still needed. It is true this hasnt ever 
*worked* although the code looks ok (with the exception of the ECP/EPP 
stuff thats in there).

I'll see if I can find some time for a bit of arm26 TLC once I've move 
house (could be 6 months though) as I'll actually have enough space to 
get the machine out of its packing box again...

  parent reply	other threads:[~2005-09-14 21:43 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
2005-09-14 21:42     ` Ian Molton [this message]
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=43289932.7090604@f2s.com \
    --to=spyro@f2s.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@osdl.org \
    --cc=domen@coderock.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philb@gnu.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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.