From: James Bottomley <James.Bottomley@steeleye.com>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] aic7* claims all checked EISA io ranges
Date: 08 Apr 2003 18:07:08 -0500 [thread overview]
Message-ID: <1049843229.2107.46.camel@mulgrave> (raw)
> 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.
> Considering how long it took for the last set of driver changes to
make
> it from -ac into kernel.org, I just assumed that this strategy was
> also failing. Is that really the only way to get updates into
Marcelo's
> tree?
I take it 2.5 is up to date, right? Because otherwise we should have
seen an update notice go across linux-scsi@vger.kernel.org.
This problem looks to be present in 2.5, so should I apply the patch?
James
next reply other threads:[~2003-04-08 22:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 23:07 James Bottomley [this message]
2003-04-08 23:12 ` [PATCH] aic7* claims all checked EISA io ranges Justin T. Gibbs
2003-04-08 23:28 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2003-04-09 1:21 [PATCH] aic7* claims all checked EISA io ranges (was: [MAILER-DAEMON@rumms.u Chuck Ebbert
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
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=1049843229.2107.46.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox