From: Joerg Roedel <joro@8bytes.org>
To: Laurent Pinchart
<laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
Cc: linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Simon Horman <horms-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>,
Nguyen Viet Dung
<nv-dung-HEF513clHfp3+QwDJ9on6Q@public.gmane.org>
Subject: Re: [PATCH 0/2] SH Mobile IOMMU fixes
Date: Tue, 07 Jan 2014 14:36:05 +0000 [thread overview]
Message-ID: <20140107143603.GE2742@8bytes.org> (raw)
In-Reply-To: <1387300730-28783-1-git-send-email-laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
On Tue, Dec 17, 2013 at 06:18:48PM +0100, Laurent Pinchart wrote:
> Hello,
>
> These two small patches fix bugs in the SH Mobile IOMMU driver that result in
> crashes at runtime. Given that the bugs have been present in the driver since
> v3.9 there's no urgency to push the fixes to v3.13.
>
> Laurent Pinchart (2):
> iommu/shmobile: Allocate archdata with kzalloc()
> iommu/shmobile: Turn the flush_lock mutex into a spinlock
>
> drivers/iommu/shmobile-iommu.c | 3 +--
> drivers/iommu/shmobile-ipmmu.c | 10 +++++-----
> drivers/iommu/shmobile-ipmmu.h | 2 +-
> 3 files changed, 7 insertions(+), 8 deletions(-)
Applied both, thanks.
next prev parent reply other threads:[~2014-01-07 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 17:18 [PATCH 0/2] SH Mobile IOMMU fixes Laurent Pinchart
[not found] ` <1387300730-28783-1-git-send-email-laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
2013-12-17 17:18 ` [PATCH 1/2] iommu/shmobile: Allocate archdata with kzalloc() Laurent Pinchart
2013-12-18 1:15 ` Simon Horman
[not found] ` <20131218011521.GI18992-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2013-12-18 14:14 ` Laurent Pinchart
2014-01-07 14:36 ` Joerg Roedel [this message]
2013-12-17 17:18 ` [PATCH 2/2] iommu/shmobile: Turn the flush_lock mutex into a spinlock Laurent Pinchart
2013-12-18 1:16 ` Simon Horman
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=20140107143603.GE2742@8bytes.org \
--to=joro@8bytes.org \
--cc=horms-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org \
--cc=linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nv-dung-HEF513clHfp3+QwDJ9on6Q@public.gmane.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).