Date: Wed, 7 Sep 2005 02:31:59 -0700
From: Andrew Morton <akpm@osdl.org>
To: marko.kohtala@gmail.com
Cc: linux-parport@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 00/10] parport: ieee1284 fixes and cleanups
Message-Id: <20050907023159.15352a82.akpm@osdl.org>
In-Reply-To: <20050905183109.284672000@kohtala.home.org>
References: <20050905183109.284672000@kohtala.home.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1080
Lines: 25

marko.kohtala@gmail.com wrote:
>
> I played with a daisy chain device that is not ieee1284 compliant
> and found buffer overflow and failure to open daisy chain devices.
> While fixing it I found also a number of other problems also affecting
> proper ieee1284 devices.
> 
> This is a collection of the changes I have made. They have been through
> linux-parport mailing list already in January and they have been modified
> according to comments.

umm, OK.  parport patches worry me because nobody seems to understand the
code any more.  We'll see.

You just sent ten patches, all with the same name.  This causes me grief
(See http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt, section 2a).

I now need to invent names for your patches, and if I later refer to one of
them you won't know which one I'm talking about.  Oh well.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/