public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [GIT PATCH] scsi bug fixes for 2.6.13
Date: Sun, 14 Aug 2005 14:48:10 -0500	[thread overview]
Message-ID: <1124048890.18802.13.camel@mulgrave> (raw)
In-Reply-To: <Pine.LNX.4.60.0508142121000.4594@poirot.grange>

On Sun, 2005-08-14 at 21:33 +0200, Guennadi Liakhovetski wrote:
> Just to make sure everyone agrees on this - there's currently a know bug 
> in dc395x with highmem reported by Pierre Ossman in thread "Kernel panic 
> with dc395x in 2.6.12.2" on linux-scsi. It is also trivial to reproduce on 
> non-highmem machines. It was there also in 2.6.12. It only was hit by one 
> person because not many use dc395x controlled cards in highmem machines 
> today. The fix is known - at least revert my patch to dc395x commited to 
> 2.6.12-rc5. This will fix this bug, leaving another one, which is much 
> harder to hit. There was only one person who hit it, but he cannot test 
> any more patches - the hardware is not there any more. I think I have a 
> fix for that one too, but that's another story. So, I would say it would 
> be worth it reverting that patch before 2.6.13, but, that's because I feel 
> personal responsibility for that bug:-)

OK, why don't we do this.  Instead of having me trawl through the trees
looking for the correct patch to reverse, why don't you attach it in an
email and I'll try to get it in to 2.6.13?

James



  reply	other threads:[~2005-08-14 19:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-04 19:43 [GIT PATCH] scsi bug fixes for 2.6.13 James Bottomley
2005-08-14 19:33 ` Guennadi Liakhovetski
2005-08-14 19:48   ` James Bottomley [this message]
2005-08-14 22:13     ` Guennadi Liakhovetski
2005-08-15  6:12     ` Guennadi Liakhovetski
2005-08-15 18:07       ` Guennadi Liakhovetski

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=1124048890.18802.13.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=akpm@osdl.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=torvalds@osdl.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