From: Nicolin Chen <nicolinc@nvidia.com>
To: Michael Shavit <mshavit@google.com>
Cc: Aahil Awatramani <aahila@google.com>, <robin.murphy@arm.com>,
<will@kernel.org>, <jgg@nvidia.com>, <joro@8bytes.org>,
<shameerali.kolothum.thodi@huawei.com>,
<yangyicong@hisilicon.com>, <jean-philippe@linaro.org>,
<linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] iommu/arm-smmu-v3: Allow default substream bypass with a pasid support
Date: Thu, 14 Sep 2023 03:26:42 -0700 [thread overview]
Message-ID: <ZQLf4uNNQ2YSnD4L@Asurada-Nvidia> (raw)
In-Reply-To: <CAKHBV25dfy2q73DmU7X6j_2XNTfgk8kbstanMczy8oZo_WFxrA@mail.gmail.com>
On Thu, Sep 14, 2023 at 05:01:58PM +0800, Michael Shavit wrote:
> On Thu, Sep 14, 2023 at 9:03 AM Nicolin Chen <nicolinc@nvidia.com> wrote:
> >
> > This has another version [1] rebased on top of Michael's refactor
> > series [2]. We'd need Michael to respin the refactor sereis and I
> > will resend mine.
>
> Just to clarify, you'd like me to rebase off master and re-send? Or do
> you mean something else by respin?
Usually we resend patches that were not accepted in the previous
cycle, rebasing on top of the new rc1. So, I would checkout the
6.6-rc1 branch and rebase the series with necessary editing, and
then send another version.
That refactor series is quite crucial for other feature series.
So, it'd be nicer to merge it as early as possible.
Thanks
Nicolin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-09-14 10:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 3:33 [PATCH v1] iommu/arm-smmu-v3: Allow default substream bypass with a pasid support Nicolin Chen
2023-06-27 9:00 ` Robin Murphy
2023-06-27 17:06 ` Nicolin Chen
2023-06-27 23:29 ` Robin Murphy
2023-06-28 0:13 ` Nicolin Chen
2023-06-28 15:39 ` Robin Murphy
2023-06-28 15:43 ` Jason Gunthorpe
2023-06-28 15:59 ` Nicolin Chen
2023-09-12 22:13 ` Aahil Awatramani
2023-09-14 1:02 ` Nicolin Chen
2023-09-14 9:01 ` Michael Shavit
2023-09-14 10:26 ` Nicolin Chen [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=ZQLf4uNNQ2YSnD4L@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=aahila@google.com \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mshavit@google.com \
--cc=robin.murphy@arm.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=will@kernel.org \
--cc=yangyicong@hisilicon.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;
as well as URLs for NNTP newsgroup(s).