All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: "James Bottomley" <James.Bottomley@SteelEye.com>,
	"Christoph Hellwig" <hch@lst.de>,
	scsi <linux-scsi@vger.kernel.org>,
	"\"Jürgen E. Fischer\"" <fischer@norbit.de>
Subject: Re: [patch 0/4] aha152x.c - Cleanup, need help in testing and auditing
Date: Tue, 24 Jul 2007 13:12:19 +0300	[thread overview]
Message-ID: <46A5D083.50803@panasas.com> (raw)
In-Reply-To: <20070719104930.7ae87df8.rdunlap@xenotime.net>

Randy Dunlap wrote:
> I prefer either of the !HIGHMEM or slave_alloc changes to adding
> a BUG_ON().  However, the SCSI people likely won't want to use the
> slave_alloc() change because then the driver may never get fixed.
> (Of course, it hasn't got fixed with the BUG happening either.)
> 
> Anyway, I'll re-read Documentation/DMA*.txt to see if I can fix it.
> 
> ---

Hi Randy.

could you please send me the patch you have with the .slave_alloc
solution for now. I would like to revise the patchset and send them
for inclusion now. They do fix some problems and let users work.
We can put a big fat warring and explanation about highmem in the
commit log comments so people can watch out.

Thanks
Boaz

  reply	other threads:[~2007-07-24 10:12 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12  9:42 [patch 0/4] aha152x.c - Cleanup, need help in testing and auditing Boaz Harrosh
2007-07-12  9:49 ` [patch 1/4] aha152x.c - Preliminary fixes and some comments Boaz Harrosh
2007-07-12  9:55 ` [patch 2/4] aha152x.c - Clean Reset path Boaz Harrosh
2007-07-12 10:05 ` [patch 3/4] aha152x.c - Fix check_condition code-path Boaz Harrosh
2007-07-12 10:09 ` [patch 4/4] aha152x.c - use data accessors and !use_sg cleanup Boaz Harrosh
2007-07-12 13:17 ` [patch 0/4] aha152x.c - Cleanup, need help in testing and auditing Boaz Harrosh
2007-07-12 20:57 ` Randy Dunlap
2007-07-16  9:22   ` Boaz Harrosh
2007-07-16  9:35     ` Christoph Hellwig
2007-07-18  0:16     ` Randy Dunlap
2007-07-18  9:29       ` Boaz Harrosh
2007-07-18 12:39         ` Boaz Harrosh
2007-07-18 17:33         ` Randy Dunlap
2007-07-18 21:58           ` Randy Dunlap
2007-07-19  2:43             ` Randy Dunlap
2007-07-19  3:03               ` Randy Dunlap
2007-07-19 13:04                 ` Boaz Harrosh
2007-07-19 15:37                   ` Randy Dunlap
2007-07-19 15:57                     ` Boaz Harrosh
2007-07-19 17:49                       ` Randy Dunlap
2007-07-24 10:12                         ` Boaz Harrosh [this message]
2007-07-24 16:17                           ` Randy Dunlap
2007-08-16  5:22                         ` Randy Dunlap
2007-08-16 14:39                           ` James Bottomley
2007-08-16 17:20                             ` Randy Dunlap
2007-08-16 17:18                               ` James Bottomley
2007-08-17 19:59                             ` Randy Dunlap

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=46A5D083.50803@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=fischer@norbit.de \
    --cc=hch@lst.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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.