mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: scameron@beardog.cca.cpqcorp.net
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, mike.miller@hp.com, axboe@kernel.dk
Subject: Re: [patch] cciss: Fix cciss SCSI rescan code to better notice device changes.
Date: Wed, 1 Oct 2008 10:12:33 -0500	[thread overview]
Message-ID: <20081001151233.GK25762@beardog.cca.cpqcorp.net> (raw)
In-Reply-To: <20080919171931.e7e7b731.akpm@linux-foundation.org>

On Fri, Sep 19, 2008 at 05:19:31PM -0700, Andrew Morton wrote:
> On Thu, 18 Sep 2008 15:07:44 -0500
[...] 
> y'know, it would be a lot simpler to just do
> 
> 	*sd = *device;
> 
> a few lines up, before assigning sd->bus/target/lun.
> 
> Putting these:
> 
> @@ -66,6 +66,10 @@ struct cciss_scsi_dev_t {
>  	int devtype;
>  	int bus, target, lun;		/* as presented to the OS */
>  	unsigned char scsi3addr[8];	/* as presented to the HW */
> +	unsigned char device_id[16];	/* from inquiry pg. 0x83 */
> +	unsigned char vendor[8];	/* bytes 8-15 of inquiry data */
> +	unsigned char model[16];	/* bytes 16-31 of inquiry data */
> +	unsigned char revision[4];	/* bytes 32-35 of inquiry data */
>  };
> 
> into a separate nested structure might make that neater still.
> 
[... and a bunch of other helpful comments. ]


Sorry for the slow reply, I've been on vacation.

Thanks for looking over my patch.  I'll try to make a 
patch to incorporate your suggestions.

> didn't cciss_scsi_add_entry() just do that?  I didn't look too closely,
> so maybe it didn't, and we're taking two copies for some reason.
> Please double-chec

I think you're right about that, good catch.

-- steve


      reply	other threads:[~2008-10-01 15:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-18 20:07 scameron
2008-09-20  0:19 ` Andrew Morton
2008-10-01 15:12   ` scameron [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=20081001151233.GK25762@beardog.cca.cpqcorp.net \
    --to=scameron@beardog.cca.cpqcorp.net \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.miller@hp.com \
    /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

all inboxes | Powered by JetHome®