[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a135090f-27e2-cf69-b3a7-c9d0e101bf07@arm.com>
Date: Thu, 28 Sep 2017 17:59:11 +0100
From: Robin Murphy <robin.murphy@....com>
To: "Raj, Ashok" <ashok.raj@...el.com>,
Casey Leedom <leedom@...lsio.com>
Cc: "joro@...tes.org" <joro@...tes.org>,
"dwmw2@...radead.org" <dwmw2@...radead.org>,
Harsh Jain <Harsh@...lsio.com>,
"herbert@...dor.apana.org.au" <herbert@...dor.apana.org.au>,
"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Michael Werner <werner@...lsio.com>,
Atul Gupta <atul.gupta@...lsio.com>
Subject: Re: [PATCH] iommu/vt-d: Fix scatterlist offset handling
On 28/09/17 14:29, Raj, Ashok wrote:
> Hi Casey
>
> On Thu, Sep 28, 2017 at 04:17:59PM +0000, Casey Leedom wrote:
>> Thanks Robin. Harsh can certainly test your latest patch as soon as he's
>> back in the office tomorrow morning India time. If your patch works and is
>> accepted, it sounds like the commit would be important enough to consider
>> backporting into various Long-Term Support releases and the affected
>> distributions. What's the procedure for nominating a commit for LTS inclusion?
I tend to leave stable decisions up to Joerg as the subsystem
maintainer, particularly when it's code outside my usual areas of
familiarity. FWIW, from a real dig through the history, the fragile
logic seems to date from the 2.6 days, having snuck in with b536d24d212c
("intel-iommu: Clean up intel_map_sg(), remove domain_page_mapping()")
> its documented in Documentation/process/submitting-patches
>
> I didn't see a new patch fly by.. Robin, could you send that over?
I hope our email server hasn't got blacklisted again... Said patch is
the top of this very thread we're replying on[1] - you were definitely
on cc :(
Robin.
[1]:https://lists.linuxfoundation.org/pipermail/iommu/2017-September/024371.html
Powered by blists - more mailing lists