All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luben Tuikov <luben_tuikov@adaptec.com>
To: Christoph Hellwig <hch@lst.de>
Cc: jejb@steeleye.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] update scsi_eh_get_sense commentary
Date: Wed, 25 Aug 2004 09:52:40 -0400	[thread overview]
Message-ID: <412C99A8.3060508@adaptec.com> (raw)
In-Reply-To: <20040824213827.GA27904@lst.de>

Very good!

Christoph Hellwig wrote:
> 
> --- 1.79/drivers/scsi/scsi_error.c      2004-06-19 16:47:16 +02:00
> +++ edited/drivers/scsi/scsi_error.c    2004-08-24 13:38:13 +02:00
> @@ -643,15 +643,13 @@
>   * Notes:
>   *    This has the unfortunate side effect that if a shost adapter does
>   *    not automatically request sense information, that we end up shutting
> - *    it down before we request it.  All shosts should be doing this
> - *    anyways, so for now all I have to say is tough noogies if you end up
> - *    in here.  On second thought, this is probably a good idea.  We
> - *    *really* want to give authors an incentive to automatically request
> - *    this.
> + *    it down before we request it.
>   *
> - *    In 2.5 this capability will be going away.
> + *    All drivers should request sense information internally these days,
> + *    so for now all I have to say is tough noogies if you end up in here.
>   *
> - *    Really?  --hch
> + *    XXX: Long term this code should go away, but that needs an audit of
> + *         all LLDDs first.
>   **/
>  static int scsi_eh_get_sense(struct list_head *work_q,
>                              struct list_head *done_q)
> -
> 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
> 


      reply	other threads:[~2004-08-25 13:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 21:38 [PATCH] update scsi_eh_get_sense commentary Christoph Hellwig
2004-08-25 13:52 ` Luben Tuikov [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=412C99A8.3060508@adaptec.com \
    --to=luben_tuikov@adaptec.com \
    --cc=hch@lst.de \
    --cc=jejb@steeleye.com \
    --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 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.