Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1276074 > unrolled thread

Re: [PATCH v5 0/6] MT8173 IOMMU SUPPORT

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH v5 0/6] MT8173 IOMMU SUPPORT Yong Wu <yong.wu@mediatek.com> - 2015-11-24 07:00 +0100
    Re: [PATCH v5 0/6] MT8173 IOMMU SUPPORT Thierry Reding <treding@nvidia.com> - 2015-11-24 11:40 +0100
      Re: [PATCH v5 0/6] MT8173 IOMMU SUPPORT Yong Wu <yong.wu@mediatek.com> - 2015-11-25 02:40 +0100

#1276074 — Re: [PATCH v5 0/6] MT8173 IOMMU SUPPORT

On Fri, 2015-10-23 at 11:26 +0200, Joerg Roedel wrote:
> On Thu, Oct 22, 2015 at 12:40:02PM +0800, Yong Wu wrote:
> >      But the mtk-iommu depend on the drivers/memory/mtk-smi.c(mtk-iommu
> > has called a function of the mtk-smi).
> >      So if there is dependence here, How should we do to merge them?
> 
> I can surely merge mtk-smi too, if it gets proper Reviewed-by and
> Acked-by tags from the maintainer(s).
> 
> 
> 	Joerg
> 
Hi Joerg,

   About the driver/memory/, We don't know who is his maintainer.
MAINTAINERS file don't have drivers/memory maintainer.
From the history in drivers/memory/ it looks like most of the
drivers land with an ack from the architecture maintainer.
And Matthias Brugger is our "ARM/Mediatek SoC support" maintainer.

Then do you mean that we need Matthias's ACK or whom others?

By the way, I will send the next version after Robin reposting
Short-descriptor. maybe in next week. 


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1276301

[Multipart message — attachments visible in raw view] — view raw

On Tue, Nov 24, 2015 at 01:58:13PM +0800, Yong Wu wrote:
> On Fri, 2015-10-23 at 11:26 +0200, Joerg Roedel wrote:
> > On Thu, Oct 22, 2015 at 12:40:02PM +0800, Yong Wu wrote:
> > >      But the mtk-iommu depend on the drivers/memory/mtk-smi.c(mtk-iommu
> > > has called a function of the mtk-smi).
> > >      So if there is dependence here, How should we do to merge them?
> > 
> > I can surely merge mtk-smi too, if it gets proper Reviewed-by and
> > Acked-by tags from the maintainer(s).
> > 
> > 
> > 	Joerg
> > 
> Hi Joerg,
> 
>    About the driver/memory/, We don't know who is his maintainer.
> MAINTAINERS file don't have drivers/memory maintainer.
> From the history in drivers/memory/ it looks like most of the
> drivers land with an ack from the architecture maintainer.
> And Matthias Brugger is our "ARM/Mediatek SoC support" maintainer.
> 
> Then do you mean that we need Matthias's ACK or whom others?

Yes, I think the sub-architecture maintainer's ACK is probably going to
be as good as it gets. Historically drivers/memory hasn't had enough of
a common ground to instate a framework.

Thierry

[toc] | [prev] | [next] | [standalone]

#1276961

On Tue, 2015-11-24 at 11:38 +0100, Thierry Reding wrote:
> On Tue, Nov 24, 2015 at 01:58:13PM +0800, Yong Wu wrote:
> > On Fri, 2015-10-23 at 11:26 +0200, Joerg Roedel wrote:
> > > On Thu, Oct 22, 2015 at 12:40:02PM +0800, Yong Wu wrote:
> > > >      But the mtk-iommu depend on the drivers/memory/mtk-smi.c(mtk-iommu
> > > > has called a function of the mtk-smi).
> > > >      So if there is dependence here, How should we do to merge them?
> > > 
> > > I can surely merge mtk-smi too, if it gets proper Reviewed-by and
> > > Acked-by tags from the maintainer(s).
> > > 
> > > 
> > > 	Joerg
> > > 
> > Hi Joerg,
> > 
> >    About the driver/memory/, We don't know who is his maintainer.
> > MAINTAINERS file don't have drivers/memory maintainer.
> > From the history in drivers/memory/ it looks like most of the
> > drivers land with an ack from the architecture maintainer.
> > And Matthias Brugger is our "ARM/Mediatek SoC support" maintainer.
> > 
> > Then do you mean that we need Matthias's ACK or whom others?
> 
> Yes, I think the sub-architecture maintainer's ACK is probably going to
> be as good as it gets. Historically drivers/memory hasn't had enough of
> a common ground to instate a framework.
> 
> Thierry

Got it.
Thanks very much for your reply.

> _______________________________________________
> Linux-mediatek mailing list
> Linux-mediatek@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-mediatek


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web