linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v3 1/4] ARM: tegra: IOMMU support for v3.19
Date: Thu, 4 Dec 2014 17:36:39 +0100	[thread overview]
Message-ID: <20141204163637.GA16914@ulmo.nvidia.com> (raw)
In-Reply-To: <2182969.Fashf5lCE4@wuerfel>

On Thu, Dec 04, 2014 at 05:21:27PM +0100, Arnd Bergmann wrote:
> On Thursday 04 December 2014 16:45:49 Thierry Reding wrote:
> > Hi ARM SoC maintainers,
> > 
> > The following changes since commit 0690cbd2e55a72a8eae557c389d1a136ed9fa142:
> > 
> >   powerpc/iommu: Rename iommu_[un]map_sg functions (2014-11-18 11:30:01 +0100)
> > 
> > are available in the git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-3.19-iommu
> > 
> > for you to fetch changes up to 8918465163171322c77a19d5258a95f56d89d2e4:
> > 
> >   memory: Add NVIDIA Tegra memory controller support (2014-12-04 16:11:47 +0100)
> > 
> > Here's a version of the pull request rebased on top of Joerg's core
> > branch from the IOMMU tree. It has the advantage of having resolved
> > the merge conflicts and the disadvantage of pulling in v3.18-rc3.
> > It also contains an updated commit description with some details
> > that ensued from a discussion regarding the DT binding as well as
> > the memory-client to SWGROUP mapping tables.
> > 
> > This pull request also contains fixes for a build error reported by the
> > 0-day builder as well as a couple of issues in the IOMMU domain detach
> > path that I've found since v2 while doing extensive driver unload and
> > reload stress testing.
> 
> Pulled into next/drivers, thanks for you patience!

Thanks,
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141204/8e8e2763/attachment.sig>

      reply	other threads:[~2014-12-04 16:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21 11:53 [GIT PULL 1/4] ARM: tegra: IOMMU support for v3.19 Thierry Reding
2014-11-21 11:53 ` [GIT PULL 2/4] ARM: tegra: Device tree changes " Thierry Reding
2014-11-26  9:10   ` [GIT PULL v2 " Thierry Reding
2014-11-21 11:53 ` [GIT PULL 3/4] ARM: tegra: Default configuration " Thierry Reding
2014-11-28 21:45   ` Arnd Bergmann
2014-11-21 11:53 ` [GIT PULL 4/4] ARM: tegra: Core code " Thierry Reding
2014-11-28 21:49   ` Arnd Bergmann
2014-12-01 13:19     ` Thierry Reding
2014-11-26  9:10 ` [GIT PULL v2 1/4] ARM: tegra: IOMMU support " Thierry Reding
2014-11-28 22:20   ` Arnd Bergmann
2014-12-01 15:05     ` Thierry Reding
2014-12-01 17:55       ` Arnd Bergmann
2014-12-02 11:51         ` Thierry Reding
2014-12-04 13:36           ` Arnd Bergmann
2014-12-04 14:43             ` Thierry Reding
2014-12-04 15:03               ` Arnd Bergmann
2014-12-04 15:45 ` [GIT PULL v3 " Thierry Reding
2014-12-04 15:45   ` [GIT PULL v3 2/4] ARM: tegra: Device tree changes " Thierry Reding
2014-12-04 16:24     ` Arnd Bergmann
2014-12-04 16:37       ` Thierry Reding
2014-12-04 16:21   ` [GIT PULL v3 1/4] ARM: tegra: IOMMU support " Arnd Bergmann
2014-12-04 16:36     ` Thierry Reding [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=20141204163637.GA16914@ulmo.nvidia.com \
    --to=thierry.reding@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).