xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: xen-devel@lists.xen.org
Cc: "Viresh Kumar" <viresh.kumar@linaro.org>,
	"Vincent Guittot" <vincent.guittot@linaro.org>,
	stratos-dev@op-lists.linaro.org,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Stefano Stabellini" <stefano.stabellini@xilinx.com>,
	"Mathieu Poirier" <mathieu.poirier@linaro.com>,
	"Oleksandr Tyshchenko" <olekstysh@gmail.com>,
	"Wei Liu" <wl@xen.org>, "Juergen Gross" <jgross@suse.com>,
	"Julien Grall" <julien@xen.org>,
	"Anthony PERARD" <anthony.perard@citrix.com>
Subject: [PATCH V6 0/3] libxl: arm: Make generic code independent of disk device
Date: Thu,  8 Sep 2022 14:22:58 +0530	[thread overview]
Message-ID: <cover.1662626550.git.viresh.kumar@linaro.org> (raw)

Hello,

This was earlier sent as part of a patch series [1] adding support for GPIO/I2C
virtio devices. The device specific patches would require some rework and
possibly several versions, and so this series separates out the generic
independent patches into a series of their own.

This series makes some of the generic code independent of the disk device, since
it can be used for other device types later on.

Rebased over staging branch from today.

V5->V6:
- Separated into a patch series of their own.
- Updated commit log of 1st patch to cover all changes.
- Rename make_virtio_mmio_node_simple() as make_virtio_mmio_node().
- New patch 3/3, separated code from device specific patch.

--
Viresh

Viresh Kumar (3):
  libxl: arm: Create alloc_virtio_mmio_params()
  libxl: arm: Split make_virtio_mmio_node()
  libxl: arm: make creation of iommu node independent of disk device

 tools/libs/light/libxl_arm.c | 83 +++++++++++++++++++++++++-----------
 1 file changed, 57 insertions(+), 26 deletions(-)

-- 
2.31.1.272.g89b43f80a514

--
Viresh

[1] https://lore.kernel.org/all/cover.1661159474.git.viresh.kumar@linaro.org/


             reply	other threads:[~2022-09-08  8:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08  8:52 Viresh Kumar [this message]
2022-09-08  8:52 ` [PATCH V6 1/3] libxl: arm: Create alloc_virtio_mmio_params() Viresh Kumar
2022-09-09 13:19   ` Anthony PERARD
2022-09-08  8:53 ` [PATCH V6 2/3] libxl: arm: Split make_virtio_mmio_node() Viresh Kumar
2022-09-09 13:21   ` Anthony PERARD
2022-09-08  8:53 ` [PATCH V6 3/3] libxl: arm: make creation of iommu node independent of disk device Viresh Kumar
2022-09-09 13:47   ` Anthony PERARD
2022-09-09 14:43   ` [PATCH V6.1 " Viresh Kumar
2022-09-09 15:02     ` Anthony PERARD
2022-09-20 10:29       ` Viresh Kumar
2022-10-04  9:59         ` Julien Grall
2022-11-24 19:19           ` Julien Grall
2022-11-25  5:45             ` Viresh Kumar
2022-11-28  9:31               ` Julien Grall
2022-09-16 10:21     ` Oleksandr

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=cover.1662626550.git.viresh.kumar@linaro.org \
    --to=viresh.kumar@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=anthony.perard@citrix.com \
    --cc=jgross@suse.com \
    --cc=julien@xen.org \
    --cc=mathieu.poirier@linaro.com \
    --cc=olekstysh@gmail.com \
    --cc=stefano.stabellini@xilinx.com \
    --cc=stratos-dev@op-lists.linaro.org \
    --cc=vincent.guittot@linaro.org \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xen.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).