All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <76306.1226@compuserve.com>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] aic7* claims all checked EISA io ranges (was: [MAILER-DAEMON@rumms.u
Date: Tue, 8 Apr 2003 21:21:30 -0400	[thread overview]
Message-ID: <200304082124_MC3-1-3399-FBD0@compuserve.com> (raw)

Justin T. Gibbs wrote:


>As far as the 2.4.X series is concerned, pushing has not helped.  I've
>seen spelling fixes and incorrorct changes get accepted from non
>maintainers "instantly", while the maintainers changes are not accepted.


And your code goes for long periods of time without merging good fixes,
like this one (from 2.4.20):


--- aic7-20030310/drivers/scsi/aic7xxx/aic7770.c.orig	Mon Mar 10 20:46:36 2003
+++ aic7-20030310/drivers/scsi/aic7xxx/aic7770.c	Tue Apr  8 20:45:20 2003
@ -314,7 +314,7 @
 	if (bootverbose)
 		printf("%s: Reading SEEPROM...", ahc_name(ahc));
 	have_seeprom = ahc_read_seeprom(&sd, (uint16_t *)sc,
-					/*start_addr*/0, sizeof(sc)/2);
+					/*start_addr*/0, sizeof(*sc)/2);
 
 	if (have_seeprom) {
 


--
 Chuck
 Can't we all just get along?

             reply	other threads:[~2003-04-09  1:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-09  1:21 Chuck Ebbert [this message]
2003-04-09  2:13 ` [PATCH] aic7* claims all checked EISA io ranges (was: [MAILER-DAEMON@rumms.u Justin T. Gibbs
2003-04-09 11:13 ` Alan Cox
2003-04-09 17:34   ` Justin T. Gibbs
2003-04-10 11:20     ` [PATCH] aic7* claims all checked EISA io ranges Stephan von Krawczynski
2003-04-10 16:44       ` Justin T. Gibbs
2003-04-11  8:51         ` Stephan von Krawczynski
2003-04-11 11:39         ` Stephan von Krawczynski
  -- strict thread matches above, loose matches on Subject: below --
2003-04-09 22:10 [PATCH] aic7* claims all checked EISA io ranges (was: [MAILER-DAEMON@rumms.u Chuck Ebbert
2003-04-10  1:48 ` carbonated beverage

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=200304082124_MC3-1-3399-FBD0@compuserve.com \
    --to=76306.1226@compuserve.com \
    --cc=gibbs@scsiguy.com \
    --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 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.