From: Joerg Roedel <joro@8bytes.org>
To: Sethi Varun-B16395 <B16395@freescale.com>
Cc: Stuart Yoder <b08248@gmail.com>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Wood Scott-B07421 <B07421@freescale.com>,
Yoder Stuart-B08248 <B08248@freescale.com>,
Kumar Gala <galak@kernel.crashing.org>
Subject: Re: [PATCH 2/6] powerpc/fsl_pci: Store the platform device information corresponding to the pci controller.
Date: Thu, 7 Mar 2013 11:37:41 +0100 [thread overview]
Message-ID: <20130307103741.GB22602@8bytes.org> (raw)
In-Reply-To: <C5ECD7A89D1DC44195F34B25E172658D3E74C7@039-SN2MPN1-013.039d.mgd.msft.net>
Yes, please base your patches on the latest upstream-tag. I will move my
tree to v3.9-rc1 soon, there are some fixes that need to go upstream.
On Thu, Mar 07, 2013 at 09:14:21AM +0000, Sethi Varun-B16395 wrote:
> Hi Joerg,
> I have to post the next version of my patchset, should I base it on top of 3.9-rc1?
> By when would you move the iommu git tree to 3.9-rc1?
>
> Regards
> Varun
>
> > -----Original Message-----
> > From: Kumar Gala [mailto:galak@kernel.crashing.org]
> > Sent: Thursday, February 28, 2013 9:15 PM
> > To: Sethi Varun-B16395
> > Cc: Joerg Roedel; Stuart Yoder; iommu@lists.linux-foundation.org;
> > linuxppc-dev@lists.ozlabs.org; linux-kernel@vger.kernel.org; Wood Scott-
> > B07421; Yoder Stuart-B08248
> > Subject: Re: [PATCH 2/6] powerpc/fsl_pci: Store the platform device
> > information corresponding to the pci controller.
> >
> >
> > On Feb 27, 2013, at 4:56 AM, Sethi Varun-B16395 wrote:
> >
> > > This patch is present in the "next branch" of linux ppc tree maintained
> > by Kumar Gala.
> > > Following is the commit id:
> > > 52c5affc545053d37c0b05224bbf70f5336caa20
> > >
> > > I am not sure if this would be part of 3.9-rc1.
> > >
> > > Regards
> > > varun
> >
> > This is now in Linus's tree so will be in 3.9-rc1
> >
> > - k
> >
>
>
next prev parent reply other threads:[~2013-03-07 10:37 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 12:52 [PATCH 0/6 v8] iommu/fsl: Freescale PAMU driver and IOMMU API implementation Varun Sethi
2013-02-18 12:52 ` [PATCH 1/6 v8] iommu/fsl: Store iommu domain information pointer in archdata Varun Sethi
2013-02-27 11:30 ` Joerg Roedel
2013-02-27 12:04 ` Sethi Varun-B16395
2013-02-28 15:51 ` Kumar Gala
2013-03-01 1:24 ` Alexey Kardashevskiy
2013-03-01 8:55 ` Sethi Varun-B16395
2013-03-01 10:07 ` Alexey Kardashevskiy
2013-03-01 16:21 ` Yoder Stuart-B08248
2013-03-04 6:35 ` Sethi Varun-B16395
2013-02-18 12:52 ` [PATCH 2/6] powerpc/fsl_pci: Store the platform device information corresponding to the pci controller Varun Sethi
2013-02-26 0:09 ` Stuart Yoder
2013-02-26 6:16 ` Sethi Varun-B16395
2013-02-27 10:45 ` Joerg Roedel
2013-02-27 10:56 ` Sethi Varun-B16395
2013-02-28 15:45 ` Kumar Gala
2013-03-07 9:14 ` Sethi Varun-B16395
2013-03-07 10:37 ` Joerg Roedel [this message]
2013-02-18 12:52 ` [PATCH 3/6] powerpc/fsl_pci: Added defines for the FSL PCI controller BRR1 register Varun Sethi
2013-02-27 11:33 ` Joerg Roedel
2013-02-28 15:46 ` Kumar Gala
2013-02-18 12:52 ` [PATCH 4/6] iommu/fsl: Add window permission flags for iommu_domain_window_enable API Varun Sethi
2013-02-18 12:52 ` [PATCH 5/6 v8] iommu/fsl: Add addtional attributes specific to the PAMU driver Varun Sethi
2013-02-27 11:38 ` Joerg Roedel
2013-02-18 12:52 ` [PATCH 6/6 v8] iommu/fsl: Freescale PAMU driver and IOMMU API implementation Varun Sethi
2013-02-19 10:04 ` Diana Craciun
2013-02-19 10:27 ` Sethi Varun-B16395
2013-02-19 15:59 ` Diana Craciun
2013-02-20 9:41 ` Sethi Varun-B16395
2013-02-26 22:33 ` Stuart Yoder
2013-02-27 11:56 ` Sethi Varun-B16395
2013-02-28 0:03 ` Stuart Yoder
2013-03-01 23:27 ` Stuart Yoder
2013-03-04 11:31 ` Sethi Varun-B16395
2013-03-04 16:55 ` Yoder Stuart-B08248
2013-02-25 10:15 ` [PATCH 0/6 " Sethi Varun-B16395
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=20130307103741.GB22602@8bytes.org \
--to=joro@8bytes.org \
--cc=B07421@freescale.com \
--cc=B08248@freescale.com \
--cc=B16395@freescale.com \
--cc=b08248@gmail.com \
--cc=galak@kernel.crashing.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).