diff for duplicates of <51E5077E.8070900@samsung.com> diff --git a/a/1.txt b/N1/1.txt index ba83a3e..7f62307 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -6,15 +6,15 @@ On 7/11/2013 4:56 PM, Grant Likely wrote: > Thanks for working on this. Comments below... > > On Wed, Jun 26, 2013 at 2:40 PM, Marek Szyprowski -> <m.szyprowski@samsung.com> wrote: +> <m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org> wrote: > > Add device tree support for contiguous memory regions defined in device > > tree. Initialization is done in 2 steps. First, the contiguous memory is > > reserved, what happens very early when only flattened device tree is > > available. Then on device initialization the corresponding cma regions are > > assigned to each device structure. > > -> > Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com> -> > Acked-by: Kyungmin Park <kyungmin.park@samsung.com> +> > Signed-off-by: Marek Szyprowski <m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org> +> > Acked-by: Kyungmin Park <kyungmin.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org> > > --- > > .../devicetree/bindings/contiguous-memory.txt | 94 ++++++++++++++ > > arch/arm/boot/dts/skeleton.dtsi | 7 +- @@ -102,9 +102,9 @@ tree? > > +base address, so if one wants to use autoconfiguration of the base > > +address, he must specify the '0' as base address in the 'reg' property > > +and assign ann uniqe name to such regions, following the convention: -> > +'region at 0', 'region at 1', 'region at 2', ... +> > +'region@0', 'region@1', 'region@2', ... > -> Drop the use of 'region'. "name at 0" is more typical. It would be +> Drop the use of 'region'. "name@0" is more typical. It would be > appropriate to have compatible = "reserved-memory-region" in each of > the reserved regions. That would avoid the problem of two regions > based at the same address having a conflict in name. diff --git a/a/content_digest b/N1/content_digest index ea576f9..1dde2e0 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,10 +1,20 @@ "ref\01372254009-25307-1-git-send-email-m.szyprowski@samsung.com\0" "ref\01372254009-25307-3-git-send-email-m.szyprowski@samsung.com\0" "ref\0CACxGe6uzau+g0gd=hkNYw1zdkfq18zt_m9OEaiJKR6=q1U4rag@mail.gmail.com\0" - "From\0m.szyprowski@samsung.com (Marek Szyprowski)\0" - "Subject\0[PATCH v3 2/2] drivers: dma-contiguous: add initialization from device tree\0" + "ref\0CACxGe6uzau+g0gd=hkNYw1zdkfq18zt_m9OEaiJKR6=q1U4rag-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org\0" + "From\0Marek Szyprowski <m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>\0" + "Subject\0Re: [PATCH v3 2/2] drivers: dma-contiguous: add initialization from device tree\0" "Date\0Tue, 16 Jul 2013 10:42:38 +0200\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>\0" + "Cc\0Sascha Hauer <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>" + devicetree-discuss <devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org> + Nishanth Peethambaran <nishanth.p-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> + Michal Nazarewicz <mina86-deATy8a+UHjQT0dZR+AlfA@public.gmane.org> + linaro-mm-sig-cunTk1MwBs8s++Sfvej+rw@public.gmane.org + Marc <marc.ceeeee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> + Kyungmin Park <kyungmin.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org> + Sylwester Nawrocki <s.nawrocki-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org> + " linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org <linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>\0" "\00:1\0" "b\0" "Hello Grant,\n" @@ -15,15 +25,15 @@ "> Thanks for working on this. Comments below...\n" ">\n" "> On Wed, Jun 26, 2013 at 2:40 PM, Marek Szyprowski\n" - "> <m.szyprowski@samsung.com> wrote:\n" + "> <m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org> wrote:\n" "> > Add device tree support for contiguous memory regions defined in device\n" "> > tree. Initialization is done in 2 steps. First, the contiguous memory is\n" "> > reserved, what happens very early when only flattened device tree is\n" "> > available. Then on device initialization the corresponding cma regions are\n" "> > assigned to each device structure.\n" "> >\n" - "> > Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>\n" - "> > Acked-by: Kyungmin Park <kyungmin.park@samsung.com>\n" + "> > Signed-off-by: Marek Szyprowski <m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>\n" + "> > Acked-by: Kyungmin Park <kyungmin.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>\n" "> > ---\n" "> > .../devicetree/bindings/contiguous-memory.txt | 94 ++++++++++++++\n" "> > arch/arm/boot/dts/skeleton.dtsi | 7 +-\n" @@ -111,9 +121,9 @@ "> > +base address, so if one wants to use autoconfiguration of the base\n" "> > +address, he must specify the '0' as base address in the 'reg' property\n" "> > +and assign ann uniqe name to such regions, following the convention:\n" - "> > +'region at 0', 'region at 1', 'region at 2', ...\n" + "> > +'region@0', 'region@1', 'region@2', ...\n" ">\n" - "> Drop the use of 'region'. \"name at 0\" is more typical. It would be\n" + "> Drop the use of 'region'. \"name@0\" is more typical. It would be\n" "> appropriate to have compatible = \"reserved-memory-region\" in each of\n" "> the reserved regions. That would avoid the problem of two regions\n" "> based at the same address having a conflict in name.\n" @@ -127,4 +137,4 @@ "Marek Szyprowski\n" Samsung R&D Institute Poland -fffeacb89d40177dc5f6c3a63bf8a8d9f09dbc9fbf50038e2df8b837a109df17 +670641dfa65272e7f832fa2552c65982fd26e3af758065059d6bf466c7903b56
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.