public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Luben Tuikov <ltuikov@yahoo.com>
To: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>
Cc: Greg KH <greg@kroah.com>,
	linux-usb@vger.kernel.org, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH take 2] [USB] Use normalized sense when emulating autosense
Date: Thu, 11 Nov 2010 10:27:11 -0800 (PST)	[thread overview]
Message-ID: <673670.8195.qm@web31801.mail.mud.yahoo.com> (raw)
In-Reply-To: <20101111174322.GB20296@one-eyed-alien.net>

--- On Thu, 11/11/10, Matthew Dharm <mdharm-kernel@one-eyed-alien.net> wrote:
> On Thu, Nov 11, 2010 at 09:07:53AM -0800, Luben Tuikov wrote:
> > 
> > Oh, I see. I'll re-post the patch then to Matthew and
> the people and lists you listed above.
> 
> Now that I'm on the CC, I see this.
> 
> What's the 10k-foot level summary here?

I'm not sure either. It's apparently the procedure of getting a patch into the linux kernel nowadays. Last time I did this was 5 years ago and in linux-scsi--I remember it being easier, again that was 5 years ago.

> Is there an alternate sense-data format that uses some sort of "descriptor" structure?

Yes. Some devices return this format of sense data for some commands.

> I'm assuming this is
> a new SCSI-III thing, or did I just miss it in SCSI-II?
> This *looks* like you're using functions provided by the
> SCSI core to
> access and modify the sense data... so I'm assuming that's
> because there
> are alternate formats...

The patch doesn't add code that modifies the sense data. That modification code is already there, the patch fixes the modification which assumed only one type of format of sense data.

The patch uses SCSI functions to abstract the sense information irrespective of the type of format of sense data.

> 
> Matt
> 
> -- 
> Matthew Dharm           
>                
>   Home: mdharm-usb@one-eyed-alien.net
> 
> Maintainer, Linux USB Mass Storage Driver
> 
> It was a new hope.
>            
>         -- Dust Puppy
> User Friendly, 12/25/1998
> 

  reply	other threads:[~2010-11-11 18:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22 21:12 [PATCH take 2] [USB] Use normalized sense when emulating autosense Luben Tuikov
2010-11-11 13:44 ` Greg KH
2010-11-11 16:49   ` Luben Tuikov
2010-11-11 16:57     ` Greg KH
2010-11-11 17:07       ` Luben Tuikov
2010-11-11 17:43         ` Matthew Dharm
2010-11-11 18:27           ` Luben Tuikov [this message]
2010-11-11 18:49             ` Matthew Dharm
2010-11-11 19:11               ` Greg KH
2010-11-11 19:50                 ` Luben Tuikov
  -- strict thread matches above, loose matches on Subject: below --
2011-09-02  6:24 Daniel J Blueman
2011-09-02 18:18 ` Greg KH
2011-09-02 19:08   ` Luben Tuikov
2011-09-02 19:22     ` Greg KH
2011-09-02 21:28       ` Luben Tuikov
2011-09-02 21:41         ` Greg KH

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=673670.8195.qm@web31801.mail.mud.yahoo.com \
    --to=ltuikov@yahoo.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mdharm-kernel@one-eyed-alien.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox