From: olekstysh@gmail.com (Oleksandr Tyshchenko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 0/2] Misc fixes for ARM page table allocator (long/short descriptor format)
Date: Thu, 16 Mar 2017 11:19:51 +0200 [thread overview]
Message-ID: <CAPD2p-=3Q7KKct29kjSi0=_-R7e3L5sgC-N4zS=BDa1vGc8uuQ@mail.gmail.com> (raw)
In-Reply-To: <1488198626-1884-1-git-send-email-olekstysh@gmail.com>
Hi, all.
Any comments?
On Mon, Feb 27, 2017 at 2:30 PM, Oleksandr Tyshchenko
<olekstysh@gmail.com> wrote:
> Hi.
>
> There is a small patch series which contains the same fix for both
> descriptor formats based on the preceding RFC patches:
> https://lists.linuxfoundation.org/pipermail/iommu/2017-February/020411.html
> https://lists.linuxfoundation.org/pipermail/iommu/2017-February/020477.html
>
> Oleksandr Tyshchenko (2):
> iommu/io-pgtable-arm: Check for leaf entry before dereferencing it
> iommu/io-pgtable-arm-v7s: Check for leaf entry before dereferencing it
>
> drivers/iommu/io-pgtable-arm-v7s.c | 6 +++++-
> drivers/iommu/io-pgtable-arm.c | 6 +++++-
> 2 files changed, 10 insertions(+), 2 deletions(-)
>
> --
> 2.7.4
>
--
Regards,
Oleksandr Tyshchenko
next prev parent reply other threads:[~2017-03-16 9:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 12:30 [PATCH v1 0/2] Misc fixes for ARM page table allocator (long/short descriptor format) Oleksandr Tyshchenko
2017-02-27 12:30 ` [PATCH v1 1/2] iommu/io-pgtable-arm: Check for leaf entry before dereferencing it Oleksandr Tyshchenko
2017-02-27 12:30 ` [PATCH v1 2/2] iommu/io-pgtable-arm-v7s: " Oleksandr Tyshchenko
2017-03-16 9:19 ` Oleksandr Tyshchenko [this message]
2017-03-16 11:19 ` [PATCH v1 0/2] Misc fixes for ARM page table allocator (long/short descriptor format) Robin Murphy
2017-03-16 11:22 ` Oleksandr Tyshchenko
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='CAPD2p-=3Q7KKct29kjSi0=_-R7e3L5sgC-N4zS=BDa1vGc8uuQ@mail.gmail.com' \
--to=olekstysh@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).