All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Ian Molton <spyro@f2s.com>
Cc: Andrew Morton <akpm@osdl.org>,
	Russell King <rmk+lkml@arm.linux.org.uk>,
	adobriyan@gmail.com, domen@coderock.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Remove drivers/parport/parport_arc.c
Date: Wed, 14 Sep 2005 23:24:11 +0100	[thread overview]
Message-ID: <1126736651.11120.2.camel@localhost.localdomain> (raw)
In-Reply-To: <43289932.7090604@f2s.com>

On Wed, 2005-09-14 at 22:42 +0100, Ian Molton wrote:
> Well unless the parport stuff changed to support ports where one cant 
> read the data latch, its still needed. 

I'm not sure I understand what you mean by that.  Can you explain what
sort of potential changes to the "parport stuff" you were thinking of?

p.



      reply	other threads:[~2005-09-14 22:24 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
2005-09-14 22:24       ` Phil Blundell [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=1126736651.11120.2.camel@localhost.localdomain \
    --to=philb@gnu.org \
    --cc=adobriyan@gmail.com \
    --cc=akpm@osdl.org \
    --cc=domen@coderock.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    --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.