public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	torvalds@transmeta.com, alan@lxorguk.ukuu.org.uk,
	marcelo@conectiva.com.br
Subject: Re: Aic7xxx 6.2.28 and Aic79xx 1.3.0 Released
Date: Thu, 23 Jan 2003 20:56:38 -0700	[thread overview]
Message-ID: <694670000.1043380598@aslan.scsiguy.com> (raw)
In-Reply-To: <20030123.193540.113447969.davem@redhat.com>

>    From: "Justin T. Gibbs" <gibbs@scsiguy.com>
>    Date: Thu, 23 Jan 2003 20:45:05 -0700
> 
>    > You keep doing this, I wish you'd stop :-)
>    
>    I wish you'd actually look at the changes before assuming
>    what they do and don't contain.
>    
> You deleted my change on at least two occaisions.
> If you've stopped doing that, great.

And when it happened the first time, you didn't bother to tell
me?  Why?  So you could act slighted later?

If you really care to have an update *stick* to a piece of externally
maintained software, pass your changes through the maintainer.  That is
only reasonable.

There have been lots of changes to the driver that I have merged back
manually and lots that I have tossed as incorrect and should never have
been accepted by Linus in the first place.  In your case, the change was
small *and* incomplete (you didn't update the aic79xx driver), so it was
missed during a few of my merges.  If you had simply bothered to send me
email when you submitted the change to Linus (you seem to know my email
address and that I maintain the driver) both drivers would have had this
change long ago.

And yes, both drivers, as of this drop, now include asm/io.h.

--
Justin


  reply	other threads:[~2003-01-24  3:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-22 22:50 Aic7xxx 6.2.28 and Aic79xx 1.3.0 Released Justin T. Gibbs
2003-01-23 12:14 ` Denis Vlasenko
2003-01-23 15:08   ` Justin T. Gibbs
2003-01-24  3:55 ` David S. Miller
2003-01-24  3:45   ` Justin T. Gibbs
2003-01-24  3:35     ` David S. Miller
2003-01-24  3:56       ` Justin T. Gibbs [this message]
2003-01-24  3:53         ` David S. Miller
2003-01-24  4:26           ` Justin T. Gibbs
2003-01-24  4:27             ` David S. Miller
2003-01-24  4:54               ` Justin T. Gibbs
2003-01-24  4:58                 ` David S. Miller

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=694670000.1043380598@aslan.scsiguy.com \
    --to=gibbs@scsiguy.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=torvalds@transmeta.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