From: Christoph Hellwig <hch@lst.de>
To: mwilck@suse.com
Cc: Mike Snitzer <snitzer@redhat.com>,
linux-scsi@vger.kernel.org, emilne@redhat.com,
Christoph Hellwig <hch@lst.de>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
Paolo Bonzini <pbonzini@redhat.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
nkoenig@redhat.com, Bart Van Assche <Bart.VanAssche@sandisk.com>,
Daniel Wagner <dwagner@suse.de>,
Alasdair G Kergon <agk@redhat.com>
Subject: Re: [dm-devel] [PATCH v4 1/3] scsi: scsi_ioctl: export __scsi_result_to_blk_status()
Date: Mon, 28 Jun 2021 11:53:41 +0200 [thread overview]
Message-ID: <20210628095341.GA4105@lst.de> (raw)
In-Reply-To: <20210628095210.26249-2-mwilck@suse.com>
On Mon, Jun 28, 2021 at 11:52:08AM +0200, mwilck@suse.com wrote:
> From: Martin Wilck <mwilck@suse.com>
>
> This makes it possible to use scsi_result_to_blk_status() from
> code that shouldn't depend on scsi_mod (e.g. device mapper).
This really has no business being used outside of low-level SCSI code.
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: mwilck@suse.com
Cc: Mike Snitzer <snitzer@redhat.com>,
Alasdair G Kergon <agk@redhat.com>,
Bart Van Assche <Bart.VanAssche@sandisk.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, dm-devel@redhat.com,
Hannes Reinecke <hare@suse.de>, Daniel Wagner <dwagner@suse.de>,
linux-block@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
Christoph Hellwig <hch@lst.de>,
Benjamin Marzinski <bmarzins@redhat.com>,
nkoenig@redhat.com, emilne@redhat.com
Subject: Re: [PATCH v4 1/3] scsi: scsi_ioctl: export __scsi_result_to_blk_status()
Date: Mon, 28 Jun 2021 11:53:41 +0200 [thread overview]
Message-ID: <20210628095341.GA4105@lst.de> (raw)
In-Reply-To: <20210628095210.26249-2-mwilck@suse.com>
On Mon, Jun 28, 2021 at 11:52:08AM +0200, mwilck@suse.com wrote:
> From: Martin Wilck <mwilck@suse.com>
>
> This makes it possible to use scsi_result_to_blk_status() from
> code that shouldn't depend on scsi_mod (e.g. device mapper).
This really has no business being used outside of low-level SCSI code.
next prev parent reply other threads:[~2021-06-28 9:54 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 9:52 [dm-devel] [PATCH v4 0/3] scsi/dm: dm_blk_ioctl(): implement failover for SG_IO on dm-multipath mwilck
2021-06-28 9:52 ` mwilck
2021-06-28 9:52 ` [dm-devel] [PATCH v4 1/3] scsi: scsi_ioctl: export __scsi_result_to_blk_status() mwilck
2021-06-28 9:52 ` mwilck
2021-06-28 9:53 ` Christoph Hellwig [this message]
2021-06-28 9:53 ` Christoph Hellwig
2021-06-28 14:57 ` [dm-devel] " Martin Wilck
2021-06-28 14:57 ` Martin Wilck
2021-06-29 12:59 ` [dm-devel] " Christoph Hellwig
2021-06-29 12:59 ` Christoph Hellwig
2021-06-29 19:23 ` [dm-devel] " Martin Wilck
2021-06-29 19:23 ` Martin Wilck
2021-06-29 21:23 ` [dm-devel] " Keith Busch
2021-06-29 21:23 ` Keith Busch
2021-06-30 8:12 ` [dm-devel] " Martin Wilck
2021-06-30 8:12 ` Martin Wilck
2021-06-30 16:01 ` [dm-devel] " Mike Snitzer
2021-06-30 16:01 ` Mike Snitzer
2021-06-30 16:54 ` [dm-devel] " Martin Wilck
2021-06-30 16:54 ` Martin Wilck
2021-06-30 22:08 ` [dm-devel] " Bart Van Assche
2021-06-30 22:08 ` Bart Van Assche
2021-07-01 6:19 ` [dm-devel] " Christoph Hellwig
2021-07-01 6:19 ` Christoph Hellwig
2021-07-06 16:40 ` [dm-devel] " Paolo Bonzini
2021-07-06 16:40 ` Paolo Bonzini
2021-06-28 9:52 ` [dm-devel] [PATCH v4 2/3] scsi: scsi_ioctl: add sg_io_to_blk_status() mwilck
2021-06-28 9:52 ` mwilck
2021-06-28 14:39 ` [dm-devel] " kernel test robot
2021-06-28 14:39 ` kernel test robot
2021-06-28 14:39 ` kernel test robot
2021-06-28 9:52 ` [dm-devel] [PATCH v4 3/3] dm mpath: add CONFIG_DM_MULTIPATH_SG_IO - failover for SG_IO mwilck
2021-06-28 9:52 ` mwilck
-- strict thread matches above, loose matches on Subject: below --
2021-06-28 16:06 [PATCH v4 2/3] scsi: scsi_ioctl: add sg_io_to_blk_status() kernel test robot
2021-06-29 7:00 ` [kbuild] " Dan Carpenter
2021-06-29 7:00 ` Dan Carpenter
2021-06-29 7:00 ` [dm-devel] " Dan Carpenter
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=20210628095341.GA4105@lst.de \
--to=hch@lst.de \
--cc=Bart.VanAssche@sandisk.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=dwagner@suse.de \
--cc=emilne@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mwilck@suse.com \
--cc=nkoenig@redhat.com \
--cc=pbonzini@redhat.com \
--cc=snitzer@redhat.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 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.