From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Corentin Labbe <clabbe.montjoie@gmail.com>
Cc: qla2xxx-upstream@qlogic.com, jejb@linux.vnet.ibm.com,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] qla2xxx: remove writeq/readq function definitions
Date: Mon, 05 Jun 2017 20:49:42 -0400 [thread overview]
Message-ID: <yq1h8zudjo9.fsf@oracle.com> (raw)
In-Reply-To: <20170602113225.24816-1-clabbe.montjoie@gmail.com> (Corentin Labbe's message of "Fri, 2 Jun 2017 13:32:25 +0200")
Corentin,
> Instead of rewriting write/readq, use linux/io-64-nonatomic-lo-hi.h
> which already have them.
Applied to 4.13/scsi-queue, thank you!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2017-06-06 0:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 11:32 [PATCH] qla2xxx: remove writeq/readq function definitions Corentin Labbe
2017-06-02 23:28 ` Bart Van Assche
2017-06-05 15:57 ` Madhani, Himanshu
2017-06-06 0:49 ` 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=yq1h8zudjo9.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=clabbe.montjoie@gmail.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=qla2xxx-upstream@qlogic.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