From: Juergen Gross <jgross@suse.com>
To: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org
Cc: "Roger Pau Monné" <roger.pau@citrix.com>,
"Jens Axboe" <axboe@kernel.dk>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH 0/4] xen/blkback: some cleanups
Date: Mon, 9 Jan 2023 16:05:12 +0100 [thread overview]
Message-ID: <055adce8-ceba-983a-19cc-b09ec30bb3c3@suse.com> (raw)
In-Reply-To: <20221216145816.27374-1-jgross@suse.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 587 bytes --]
On 16.12.22 15:58, Juergen Gross wrote:
> Some small cleanup patches I had lying around for some time now.
>
> Juergen Gross (4):
> xen/blkback: fix white space code style issues
> xen/blkback: remove stale prototype
> xen/blkback: simplify free_persistent_gnts() interface
> xen/blkback: move blkif_get_x86_*_req() into blkback.c
>
> drivers/block/xen-blkback/blkback.c | 126 +++++++++++++++++++++++++---
> drivers/block/xen-blkback/common.h | 103 +----------------------
> 2 files changed, 118 insertions(+), 111 deletions(-)
>
Ping?
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3149 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2023-01-09 15:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 14:58 [PATCH 0/4] xen/blkback: some cleanups Juergen Gross
2022-12-16 14:58 ` [PATCH 1/4] xen/blkback: fix white space code style issues Juergen Gross
2022-12-16 14:58 ` [PATCH 2/4] xen/blkback: remove stale prototype Juergen Gross
2022-12-16 14:58 ` [PATCH 3/4] xen/blkback: simplify free_persistent_gnts() interface Juergen Gross
2022-12-16 14:58 ` [PATCH 4/4] xen/blkback: move blkif_get_x86_*_req() into blkback.c Juergen Gross
2023-03-14 14:00 ` Roger Pau Monné
2023-01-09 15:05 ` Juergen Gross [this message]
2023-03-14 12:18 ` [PATCH 0/4] xen/blkback: some cleanups Juergen Gross
2023-03-14 14:01 ` Roger Pau Monné
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=055adce8-ceba-983a-19cc-b09ec30bb3c3@suse.com \
--to=jgross@suse.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roger.pau@citrix.com \
--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.