All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: "Jernej Škrabec" <jernej.skrabec@gmail.com>,
	will@kernel.org, iommu@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org, m.szyprowski@samsung.com,
	heiko@sntech.de, thierry.reding@gmail.com, vdumpa@nvidia.com
Subject: Re: [PATCH 0/8] iommu: Clean up map/unmap ops
Date: Tue, 26 Sep 2023 16:57:25 +0200	[thread overview]
Message-ID: <ZRLxVQb1zUqKTJNd@8bytes.org> (raw)
In-Reply-To: <d88b244f-75b2-6b22-109e-7429b4c8d77c@arm.com>

On Tue, Sep 26, 2023 at 01:01:28PM +0100, Robin Murphy wrote:
> No functional issue, and TBH I think there's no harm in avoiding the
> dependency (I was kind of assuming you would pick this series to the core
> branch, so the "placeholder" status might extend that far too) - it should
> just mean that when you pick Jernej's patch to a topic branch you'll get a
> conflict merging it to core, and the correct resolution will be to take
> everything from that branch and replace my patch.

Alright, thanks for clarifying. I hereby ask Jernej to base his new
patch on the core branch, once I published it (which should be later
today).

Regards,

	Joerg

WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: "Jernej Škrabec" <jernej.skrabec@gmail.com>,
	will@kernel.org, iommu@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org, m.szyprowski@samsung.com,
	heiko@sntech.de, thierry.reding@gmail.com, vdumpa@nvidia.com
Subject: Re: [PATCH 0/8] iommu: Clean up map/unmap ops
Date: Tue, 26 Sep 2023 16:57:25 +0200	[thread overview]
Message-ID: <ZRLxVQb1zUqKTJNd@8bytes.org> (raw)
In-Reply-To: <d88b244f-75b2-6b22-109e-7429b4c8d77c@arm.com>

On Tue, Sep 26, 2023 at 01:01:28PM +0100, Robin Murphy wrote:
> No functional issue, and TBH I think there's no harm in avoiding the
> dependency (I was kind of assuming you would pick this series to the core
> branch, so the "placeholder" status might extend that far too) - it should
> just mean that when you pick Jernej's patch to a topic branch you'll get a
> conflict merging it to core, and the correct resolution will be to take
> everything from that branch and replace my patch.

Alright, thanks for clarifying. I hereby ask Jernej to base his new
patch on the core branch, once I published it (which should be later
today).

Regards,

	Joerg

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-09-26 14:57 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12 16:18 [PATCH 0/8] iommu: Clean up map/unmap ops Robin Murphy
2023-09-12 16:18 ` Robin Murphy
2023-09-12 16:18 ` [PATCH 1/8] iommu/exynos: Update to {map,unmap}_pages Robin Murphy
2023-09-12 16:18   ` Robin Murphy
2023-09-12 16:18 ` [PATCH 2/8] iommu/omap: " Robin Murphy
2023-09-12 16:18   ` Robin Murphy
2023-09-12 16:18 ` [PATCH 3/8] iommu/rockchip: " Robin Murphy
2023-09-12 16:18   ` Robin Murphy
2023-09-12 16:18 ` [PATCH 4/8] iommu/sun50i: " Robin Murphy
2023-09-12 16:18   ` Robin Murphy
2023-09-12 16:18 ` [PATCH 5/8] iommu/tegra-gart: " Robin Murphy
2023-09-12 16:18   ` Robin Murphy
2023-09-12 16:18 ` [PATCH 6/8] iommu/tegra-smmu: " Robin Murphy
2023-09-12 16:18   ` Robin Murphy
2023-09-12 16:18 ` [PATCH 7/8] iommu: Retire map/unmap ops Robin Murphy
2023-09-12 16:18   ` Robin Murphy
2023-09-13 14:40   ` Jason Gunthorpe
2023-09-13 14:40     ` Jason Gunthorpe
2023-09-12 16:18 ` [PATCH 8/8] iommu: Improve map/unmap sanity checks Robin Murphy
2023-09-12 16:18   ` Robin Murphy
2023-09-13 14:39   ` Jason Gunthorpe
2023-09-13 14:39     ` Jason Gunthorpe
2023-09-13 18:46     ` Robin Murphy
2023-09-13 18:46       ` Robin Murphy
2023-09-14 12:48       ` Jason Gunthorpe
2023-09-14 12:48         ` Jason Gunthorpe
2023-09-14 14:23         ` Robin Murphy
2023-09-14 14:23           ` Robin Murphy
2023-09-14 16:48           ` Jason Gunthorpe
2023-09-14 16:48             ` Jason Gunthorpe
2023-09-19 12:18             ` Robin Murphy
2023-09-19 12:18               ` Robin Murphy
2023-09-22 17:28               ` Jason Gunthorpe
2023-09-22 17:28                 ` Jason Gunthorpe
2023-09-25 10:05 ` [PATCH 0/8] iommu: Clean up map/unmap ops Joerg Roedel
2023-09-25 10:05   ` Joerg Roedel
2023-09-25 15:33   ` Jernej Škrabec
2023-09-25 15:33     ` Jernej Škrabec
2023-09-26  9:23     ` Joerg Roedel
2023-09-26  9:23       ` Joerg Roedel
2023-09-26 12:01       ` Robin Murphy
2023-09-26 12:01         ` Robin Murphy
2023-09-26 14:57         ` Joerg Roedel [this message]
2023-09-26 14:57           ` Joerg Roedel

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=ZRLxVQb1zUqKTJNd@8bytes.org \
    --to=joro@8bytes.org \
    --cc=heiko@sntech.de \
    --cc=iommu@lists.linux.dev \
    --cc=jernej.skrabec@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=m.szyprowski@samsung.com \
    --cc=robin.murphy@arm.com \
    --cc=thierry.reding@gmail.com \
    --cc=vdumpa@nvidia.com \
    --cc=will@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 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.