linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Stewart <andystewart@comcast.net>
To: Andrew Morton <akpm@osdl.org>
Cc: jgarzik@pobox.com, linux-kernel@vger.kernel.org,
	linux-ide@vger.kernel.org
Subject: Re: enable-reads-on-plextor-712-sa-on-26115.patch added to -mm tree
Date: Mon, 23 May 2005 20:44:39 -0400	[thread overview]
Message-ID: <429278F7.70008@comcast.net> (raw)
In-Reply-To: <20050523173420.22281325.akpm@osdl.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


HI Andrew,

Andrew Morton wrote:
> Andy Stewart <andystewart@comcast.net> wrote:
>>>Good show.
>>Aw, come on, Jeff.  I gave it a shot,
> 
> You did, and that's very much appreciated, thanks.

Thank you for the encouraging words.  :-)

> 
>>If you believe this patch is
>>inappropriate, then please ask Andrew Morton to remove it
> 
> I already have removed it, but only because it appears that the patch might
> cause regressions in other areas.

I agree that my patch should be removed if it is breaking other things.
Thanks for taking it out.

> 
> Basically it goes like this:
> 
> - Someone sends a patch
> 
> - Patch gets ignored.
> 
> - I merge it, without even looking at the thing.
> 
> I do this as a reminder to myself and to other developers that there is
> some kernel bug or shortcoming.  Basically, it's a bug-tracking system. 
> Periodically I'll spam the maintainer with the patch and eventually he'll
> tell me to drop the thing because the problem is fixed, or he'll tell the
> originator why the patch will never be merged.
> 
> Either way, the patch (and the problem which caused you to write the patch)
> gets some sort of definite dispositive handling, rather than falling
> through a crack.

Thank you for the explaination, and for the feedback to let me know that
the patch didn't fall through the cracks.

Andy

- --
Andy Stewart, Founder
Worcester Linux Users' Group
Worcester, MA, USA
http://www.wlug.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCknj3Hl0iXDssISsRApp1AJ97vyP5CGavkNmP0TIHL4yvVga6nwCdFL1+
wYN6ergAnBeboO0OQK9/NBo=
=RwPj
-----END PGP SIGNATURE-----

  reply	other threads:[~2005-05-24  0:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200505232245.j4NMjtk4024089@shell0.pdx.osdl.net>
2005-05-23 23:09 ` enable-reads-on-plextor-712-sa-on-26115.patch added to -mm tree Jeff Garzik
2005-05-24  0:24   ` Andy Stewart
2005-05-24  0:34     ` Andrew Morton
2005-05-24  0:44       ` Andy Stewart [this message]
2005-05-24  3:30     ` Jeff Garzik

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=429278F7.70008@comcast.net \
    --to=andystewart@comcast.net \
    --cc=akpm@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).