From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Juergen Gross <jgross@suse.com>
Cc: Geliang Tang <geliangtang@gmail.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
xen-devel@lists.xenproject.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xen/scsifront: use offset_in_page() macro
Date: Mon, 24 Apr 2017 18:15:02 -0400 [thread overview]
Message-ID: <yq17f29ihax.fsf@oracle.com> (raw)
In-Reply-To: <ca4bb9e8-b614-a24d-e533-70ce75ff288f@suse.com> (Juergen Gross's message of "Mon, 24 Apr 2017 07:05:16 +0200")
Juergen,
> On 22/04/17 03:21, Geliang Tang wrote:
>> Use offset_in_page() macro instead of open-coding.
>>
>> Signed-off-by: Geliang Tang <geliangtang@gmail.com>
>
> Reviewed-by: Juergen Gross <jgross@suse.com>
Taking this through the Xen tree or should I queue it?
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2017-04-24 22:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-22 1:21 [PATCH] fs/ocfs2/cluster: use offset_in_page() macro Geliang Tang
2017-04-22 1:21 ` [PATCH] gdth: " Geliang Tang
2017-04-22 1:21 ` [PATCH] net: atheros: atl1: " Geliang Tang
2017-04-24 17:58 ` David Miller
2017-04-22 1:21 ` [PATCH] serial: pch_uart: " Geliang Tang
2017-04-22 1:21 ` [PATCH] tty/serial: atmel: " Geliang Tang
2017-04-24 7:12 ` Richard Genoud
2017-04-29 1:39 ` [PATCH v2] " Geliang Tang
2017-05-02 8:47 ` Richard Genoud
2017-04-22 1:21 ` [PATCH] xen/scsifront: " Geliang Tang
2017-04-24 5:05 ` Juergen Gross
2017-04-24 22:15 ` Martin K. Petersen [this message]
2017-04-25 5:07 ` Juergen Gross
2017-04-25 5:07 ` Juergen Gross
2017-04-24 22:15 ` Martin K. Petersen
2017-04-24 5:05 ` Juergen Gross
2017-04-25 6:58 ` Juergen Gross
2017-04-25 6:58 ` Juergen Gross
2017-04-22 1:21 ` Geliang Tang
2017-04-22 1:21 ` [PATCH] xprtrdma: " Geliang Tang
2017-04-22 3:37 ` Chuck Lever
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=yq17f29ihax.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=geliangtang@gmail.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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.