diff for duplicates of <20111122191226.GA4844@kroah.com> diff --git a/a/1.txt b/N1/1.txt index 055d6a7..4efece0 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -3,15 +3,15 @@ On Tue, Nov 22, 2011 at 10:09:29AM -0800, Mike Turquette wrote: > <linux@arm.linux.org.uk> wrote: > > On Tue, Nov 22, 2011 at 07:42:59AM -0800, Greg KH wrote: > >> On Mon, Nov 21, 2011 at 05:40:42PM -0800, Mike Turquette wrote: -> >> > .sysfs support. Visualize your clk tree at /sys/clk! Where would be +> >> > ? .sysfs support. ?Visualize your clk tree at /sys/clk! ?Where would be > >> > a better place to put the clk tree besides the root of /sys/? > >> > >> Um, in the "proper" place for it under /sys/devices like the rest of the > >> device tree is? > > > > I'd suggest that making the clock tree visible in sysfs (and therefore -> > part of the kernel ABI) is not a good idea. Some of the nodes in there -> > will be specific to the implementation. Exposing the clock nodes means +> > part of the kernel ABI) is not a good idea. ?Some of the nodes in there +> > will be specific to the implementation. ?Exposing the clock nodes means > > that if you have to change the clock tree structure, you change the > > visible userspace ABI. > diff --git a/a/content_digest b/N1/content_digest index 9e6146f..d462b16 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,32 +2,10 @@ "ref\020111122154259.GA18954@kroah.com\0" "ref\020111122174544.GA19739@n2100.arm.linux.org.uk\0" "ref\0CAPtuhTgFPZA9U-8heNw1eNUnHLFv2w+LzXg5rdjSx3J53Xy+2g@mail.gmail.com\0" - "From\0Greg KH <greg@kroah.com>\0" - "Subject\0Re: [PATCH v3 0/5] common clk framework\0" + "From\0greg@kroah.com (Greg KH)\0" + "Subject\0[PATCH v3 0/5] common clk framework\0" "Date\0Tue, 22 Nov 2011 11:12:26 -0800\0" - "To\0Mike Turquette <mturquette@linaro.org>\0" - "Cc\0Russell King - ARM Linux <linux@arm.linux.org.uk>" - Mike Turquette <mturquette@ti.com> - linux-kernel@vger.kernel.org - linux-omap@vger.kernel.org - linux-arm-kernel@lists.infradead.org - jeremy.kerr@canonical.com - broonie@opensource.wolfsonmicro.com - tglx@linutronix.de - linus.walleij@stericsson.com - amit.kucheria@linaro.org - dsaxena@linaro.org - patches@linaro.org - linaro-dev@lists.linaro.org - paul@pwsan.com - grant.likely@secretlab.ca - sboyd@quicinc.com - shawn.guo@freescale.com - skannan@quicinc.com - magnus.damm@gmail.com - arnd.bergmann@linaro.org - eric.miao@linaro.org - " richard.zhao@linaro.org\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On Tue, Nov 22, 2011 at 10:09:29AM -0800, Mike Turquette wrote:\n" @@ -35,15 +13,15 @@ "> <linux@arm.linux.org.uk> wrote:\n" "> > On Tue, Nov 22, 2011 at 07:42:59AM -0800, Greg KH wrote:\n" "> >> On Mon, Nov 21, 2011 at 05:40:42PM -0800, Mike Turquette wrote:\n" - "> >> > \302\240 .sysfs support. \302\240Visualize your clk tree at /sys/clk! \302\240Where would be\n" + "> >> > ? .sysfs support. ?Visualize your clk tree at /sys/clk! ?Where would be\n" "> >> > a better place to put the clk tree besides the root of /sys/?\n" "> >>\n" "> >> Um, in the \"proper\" place for it under /sys/devices like the rest of the\n" "> >> device tree is?\n" "> >\n" "> > I'd suggest that making the clock tree visible in sysfs (and therefore\n" - "> > part of the kernel ABI) is not a good idea. \302\240Some of the nodes in there\n" - "> > will be specific to the implementation. \302\240Exposing the clock nodes means\n" + "> > part of the kernel ABI) is not a good idea. ?Some of the nodes in there\n" + "> > will be specific to the implementation. ?Exposing the clock nodes means\n" "> > that if you have to change the clock tree structure, you change the\n" "> > visible userspace ABI.\n" "> \n" @@ -75,4 +53,4 @@ "\n" greg k-h -19d8797765c629ab9174400c4f13f7ea1c258af00b9a96172d86e9214f0d4b49 +f4bdd25a2588a4ebfb9fd1ee5a3028b6518ae3376936c7b8d7c35e0c6d807298
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.