From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [GIT PULL FOR v3.16] SH-Mobile IPMMU miscellaneous cleanups
Date: Mon, 12 May 2014 19:46:57 +0000 [thread overview]
Message-ID: <3320346.ObYc3HAjHb@avalon> (raw)
In-Reply-To: <20140512185554.GY12376-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
Hi Joerg,
On Monday 12 May 2014 20:55:54 Joerg Roedel wrote:
> On Thu, Apr 17, 2014 at 12:18:21PM +0200, Laurent Pinchart wrote:
> > git://linuxtv.org/pinchartl/fbdev.git iommu/for-v3.16
>
> Pulled, thanks Laurent,
Thank you. Now, what about the "iommu: Add driver for Renesas VMSA-compatible
IPMMU" patch ? :-)
> despite I missed a MAINTAINERS patch ;-)
Since when are developers required to become maintainers when submitting the
odd cleanup patch ? :-)
> What happened to the original author of this driver?
I'm afraid I don't know. Magnus (CC'ed) might have more information.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2014-05-12 19:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 23:49 [PATCH 0/3] SH-Mobile IPMMU miscellaneous cleanups Laurent Pinchart
2014-04-02 23:49 ` [PATCH 1/3] iommu/shmobile: Depend on ARCH_SHMOBILE Laurent Pinchart
2014-04-02 23:49 ` [PATCH 2/3] iommu/shmobile: Don't ignore the ipmmu_iommu_init() return value Laurent Pinchart
2014-04-02 23:49 ` [PATCH 3/3] iommu/shmobile: Use devm_ioremap_resource() Laurent Pinchart
[not found] ` <1396482562-1851-1-git-send-email-laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
2014-04-17 10:18 ` [GIT PULL FOR v3.16] SH-Mobile IPMMU miscellaneous cleanups Laurent Pinchart
2014-05-12 18:55 ` Joerg Roedel
[not found] ` <20140512185554.GY12376-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2014-05-12 19:46 ` Laurent Pinchart [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=3320346.ObYc3HAjHb@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
--cc=linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@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).