From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Christoph Hellwig <hch@infradead.org>,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
James.Bottomley@suse.de, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH]: Fix Ultrastor asm snippet
Date: Tue, 24 May 2011 13:28:44 -0400 [thread overview]
Message-ID: <1306258124.10201.22.camel@mulgrave.site> (raw)
In-Reply-To: <20110520142459.4c37d3e0@lxorguk.ukuu.org.uk>
On Fri, 2011-05-20 at 14:24 +0100, Alan Cox wrote:
> On Fri, 20 May 2011 09:02:15 -0400
> Christoph Hellwig <hch@infradead.org> wrote:
>
> > On Wed, May 18, 2011 at 05:06:05PM +0200, Samuel Thibault wrote:
> > > Commit 1292500b replaced
> > >
> > > "=m" (*field) : "1" (*field)
> > >
> > > with
> > >
> > > "=m" (*field) :
> > >
> > > with comment "The following patch fixes it by using the '+' operator on
> > > the (*field) operand, marking it as read-write to gcc."
> > > '+' was actually forgotten. This really puts it.
> >
> > Do you actually have the hardware or was this just a code audit?
> >
> > I have the strong suspicion that this driver is pretty much dead and
> > bitrotting.
>
> There are a pile of scsi drivers like the Ultrastor that probably want
> retiring via staging.
OK, can someone work out how we do this and then send the patch (I
assume it's just an update in the deprecated features and a move to
staging?)
> I can believe an AHA152x or two lurk around,
Yes, got one ... and occasionally even test with it.
> and the odd NCR53c80 and
> clones because they were so voluminous but the rest I doubt somewhat.
James
prev parent reply other threads:[~2011-05-24 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 15:06 [PATCH]: Fix Ultrastor asm snippet Samuel Thibault
2011-05-20 13:02 ` Christoph Hellwig
2011-05-20 13:04 ` Samuel Thibault
2011-05-20 13:24 ` Alan Cox
2011-05-24 17:28 ` James Bottomley [this message]
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=1306258124.10201.22.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=James.Bottomley@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=samuel.thibault@ens-lyon.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).