From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: John Pittman <jpittman@redhat.com>
Cc: jejb@linux.vnet.ibm.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sd: Cleaned up comment references to @sdp argument explanation.
Date: Fri, 20 Jan 2017 16:59:39 -0500 [thread overview]
Message-ID: <yq160l9ie9g.fsf@oracle.com> (raw)
In-Reply-To: <1484255840-29950-1-git-send-email-jpittman@redhat.com> (John Pittman's message of "Thu, 12 Jan 2017 16:17:20 -0500")
>>>>> "John" == John Pittman <jpittman@redhat.com> writes:
John> In sd.c there are two comment references to 'struct scsi_device
John> *sdp' as an argument. One of the references has a typo and the
John> other should be a reference to 'struct device *dev' instead.
Applied to 4.11/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2017-01-20 21:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 21:17 [PATCH] sd: Cleaned up comment references to @sdp argument explanation John Pittman
2017-01-20 21:59 ` Martin K. Petersen [this message]
2017-01-12 21:24 John Pittman
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=yq160l9ie9g.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=jpittman@redhat.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;
as well as URLs for NNTP newsgroup(s).