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
Date: Wed, 7 Sep 2005 02:31:59 -0700 [thread overview]
Message-ID: <20050907023159.15352a82.akpm@osdl.org> (raw)
In-Reply-To: <20050905183109.284672000@kohtala.home.org>
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.
next prev parent reply other threads:[~2005-09-07 9:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-05 18:31 marko.kohtala
2005-09-05 18:31 ` [patch 01/10] " marko.kohtala
2005-09-05 18:31 ` [patch 02/10] " marko.kohtala
2005-09-05 18:31 ` [patch 03/10] " marko.kohtala
2005-09-05 18:31 ` [patch 04/10] " marko.kohtala
2005-09-05 18:31 ` [patch 05/10] " marko.kohtala
2005-09-05 18:31 ` [patch 06/10] " marko.kohtala
2005-09-05 18:31 ` [patch 07/10] " marko.kohtala
2005-09-05 18:31 ` [patch 08/10] " marko.kohtala
2005-09-05 18:31 ` [patch 09/10] " marko.kohtala
2005-09-05 18:31 ` [patch 10/10] " marko.kohtala
2005-09-07 9:31 ` Andrew Morton [this message]
2005-09-07 11:34 ` [patch 00/10] " Marko Kohtala
2005-09-07 11:50 ` Andrew Morton
2005-09-08 3:07 ` Dmitry Torokhov
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=20050907023159.15352a82.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parport@lists.infradead.org \
--cc=marko.kohtala@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®