linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	Ed Lin <ed.lin@promise.com>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/0] scsi_cmnd accessors issues
Date: Sun, 17 Jun 2007 12:45:17 +0300	[thread overview]
Message-ID: <467502AD.6090309@panasas.com> (raw)
In-Reply-To: <46716C45.1090107@panasas.com>

Boaz Harrosh wrote:
> FUJITA Tomonori wrote:
>> There are just two llds. I suspect that we can fix them. Or they can
>> access to the data directly (without the accessors) if we can't.
>>
>> I don't think that introducing something like scsi_set_sg_count, which
>> is meaningless to most of llds, is a good idea.
> 
> Following are 3 patches for fixing the l-value issues for accessors.
> 
> 0/1 - proposed new accessors which will not let l-value code compile.
> 0/2 - Clean fix of drivers/scsi/tmscsim.c to not need setting of sg_count
> 0/3 - In drivers/scsi/stex.c open code of write access to request_bufflen.
>       when new code is committed this driver will have to change with it.
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


Hi Tomo.

I do not understand.
- Do you not accept my first patch. This is to go in now for  2.6.23.
  It is for protection against out-of-tree and the rest of the not
  converted drivers. To not use new accessors as l-value.

- Guennadi have you had a look at second patch it is clear that SavedSGCount
  is no longer used and that scsi_sg_count(pcmd) needs not be saved since it
  never changes.

- Tomo, Ed. The 3rd patch was sent so the first patch can be accepted now. As
  stated, it is a fix to the first cleanup patch that wrongfully used scsi_bufflen
  as l-value.

Boaz


  parent reply	other threads:[~2007-06-17  9:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12 18:02 scsi_cmnd accessors issues Boaz Harrosh
2007-06-12 18:46 ` Boaz Harrosh
2007-06-12 23:51 ` FUJITA Tomonori
2007-06-13 10:32   ` Harrosh, Boaz
2007-06-13 10:45     ` FUJITA Tomonori
2007-06-14 16:26       ` [PATCH 0/0] " Boaz Harrosh
2007-06-14 16:33         ` [PATCH 1/3] Restrict scsi accessors access to read-only Boaz Harrosh
2007-06-14 18:50           ` Jeff Garzik
2007-06-14 16:33         ` [PATCH 2/3] Farther clean-up of tmscsim driver Boaz Harrosh
2007-06-17 18:15           ` Guennadi Liakhovetski
2007-06-14 16:33         ` [PATCH 3/3] Farther clean up of stex.c driver Boaz Harrosh
2007-06-17  9:45         ` Boaz Harrosh [this message]
2007-06-18 14:24           ` [PATCH 0/0] scsi_cmnd accessors issues FUJITA Tomonori
2007-06-18 15:24             ` Harrosh, Boaz
2007-06-13 11:24 ` FUJITA Tomonori
2007-06-13 15:41   ` FUJITA Tomonori
2007-06-16  8:45 ` 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=467502AD.6090309@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=ed.lin@promise.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).