From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: James Bottomley <jejb@linux.ibm.com>,
Martin Petersen <martin.petersen@oracle.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/7] SCSI: cleanup debugfs usage
Date: Tue, 29 Jan 2019 00:37:47 -0500 [thread overview]
Message-ID: <yq1zhrkdnx0.fsf@oracle.com> (raw)
In-Reply-To: <20190122150906.12470-1-gregkh@linuxfoundation.org> (Greg Kroah-Hartman's message of "Tue, 22 Jan 2019 16:08:59 +0100")
Greg,
> When calling debugfs code, there is no need to ever check the return
> value of the call, as no logic should ever change if a call works
> properly or not. Fix up a bunch of x86-specific code to not care
> about the results of debugfs.
Applied to 5.1/scsi-queue, thank you!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2019-01-29 5:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 15:08 [PATCH 0/7] SCSI: cleanup debugfs usage Greg Kroah-Hartman
2019-01-22 15:09 ` [PATCH 1/7] scsi: bfa: no need to check return value of debugfs_create functions Greg Kroah-Hartman
2019-01-22 15:09 ` [PATCH 2/7] scsi: csiostor: " Greg Kroah-Hartman
2019-01-24 9:22 ` Johannes Thumshirn
2019-01-22 15:09 ` [PATCH 3/7] scsi: fnic: " Greg Kroah-Hartman
2019-01-22 18:05 ` Satish Kharat (satishkh)
2019-01-22 15:09 ` [PATCH 4/7] scsi: snic: " Greg Kroah-Hartman
2019-01-22 15:09 ` [PATCH 5/7] scsi: lpfc: " Greg Kroah-Hartman
2019-01-22 15:09 ` [PATCH 6/7] scsi: qlogic: " Greg Kroah-Hartman
2019-01-23 5:36 ` Manish Rangankar
2019-01-22 15:09 ` [PATCH 7/7] scsi: qla2xxx: " Greg Kroah-Hartman
2019-01-23 9:23 ` [PATCH 0/7] SCSI: cleanup debugfs usage John Garry
2019-01-29 5:37 ` Martin K. Petersen [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=yq1zhrkdnx0.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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