diff for duplicates of <20150818002018.31346.63666@quantum> diff --git a/a/1.txt b/N1/1.txt index 5c98ee8..6772812 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -6,35 +6,24 @@ Quoting Geert Uytterhoeven (2015-08-04 05:34:06) > >> +++ b/arch/arm64/boot/dts/renesas/r8a7795.dtsi > >> @@ -0,0 +1,93 @@ > >> +/ { -> = - +> > >> + clocks { > > -> > Let's try to make it right from the start on Gen3. The CPG node should = -be a -> > direct child of the bus node mentioned above, and the MSTP clocks shoul= -d be +> > Let's try to make it right from the start on Gen3. The CPG node should be a +> > direct child of the bus node mentioned above, and the MSTP clocks should be > > children of the CPG node. -> = - +> > Agreed. -> = - -> > I'm not sure where to put the non-memory-mapped clocks though, should t= -hey be -> > directly under the root node ? It would make sense for extal_clk, but h= -ow -> > about the fixed-factor clocks ? Should they be children of the CPG node= - too ? -> = - -> I believe the current trend is to put clocks like "extal_clk" under the r= -oot +> +> > I'm not sure where to put the non-memory-mapped clocks though, should they be +> > directly under the root node ? It would make sense for extal_clk, but how +> > about the fixed-factor clocks ? Should they be children of the CPG node too ? +> +> I believe the current trend is to put clocks like "extal_clk" under the root > node. > As the fixed-factor clocks are generated by the CPG module, and we do have > a device node for it, I'd make them children of the CPG node, too. -> = - +> > Any comments from the clk+dt experts? I don't know if anyone is an expert ;-) @@ -66,67 +55,57 @@ expressing your clock data with C inside of your provider driver. Regards, Mike -> = - +> > Thanks! -> = - -> >> + #address-cells =3D <2>; -> >> + #size-cells =3D <2>; +> +> >> + #address-cells = <2>; +> >> + #size-cells = <2>; > >> + ranges; > >> + > >> + extal_clk: extal_clk { -> >> + compatible =3D "fixed-clock"; -> >> + #clock-cells =3D <0>; -> >> + clock-frequency =3D <0>; -> >> + clock-output-names =3D "extal"; +> >> + compatible = "fixed-clock"; +> >> + #clock-cells = <0>; +> >> + clock-frequency = <0>; +> >> + clock-output-names = "extal"; > >> + }; > >> + cpg_clocks: cpg_clocks@e6150000 { -> >> + compatible =3D "renesas,r8a7795-cpg-clocks", +> >> + compatible = "renesas,r8a7795-cpg-clocks", > >> + "renesas,rcar-gen3-cpg-clocks"; -> >> + reg =3D <0 0xe6150000 0 0x1000>; -> >> + clocks =3D <&extal_clk>; -> >> + #clock-cells =3D <1>; -> >> + clock-output-names =3D "main", "pll0", "pll1","p= -ll2", +> >> + reg = <0 0xe6150000 0 0x1000>; +> >> + clocks = <&extal_clk>; +> >> + #clock-cells = <1>; +> >> + clock-output-names = "main", "pll0", "pll1","pll2", > >> + "pll3", "pll4"; > >> + }; > >> + p_clk: p_clk { -> >> + compatible =3D "fixed-factor-clock"; -> >> + clocks =3D <&cpg_clocks RCAR_GEN3_CLK_PLL1>; -> >> + #clock-cells =3D <0>; -> >> + clock-div =3D <24>; -> >> + clock-mult =3D <1>; -> >> + clock-output-names =3D "p"; +> >> + compatible = "fixed-factor-clock"; +> >> + clocks = <&cpg_clocks RCAR_GEN3_CLK_PLL1>; +> >> + #clock-cells = <0>; +> >> + clock-div = <24>; +> >> + clock-mult = <1>; +> >> + clock-output-names = "p"; > >> + }; > >> + mstp3_clks: mstp3_clks@e615013c { -> >> + compatible =3D "renesas,r8a7795-mstp-clocks", +> >> + compatible = "renesas,r8a7795-mstp-clocks", > >> + "renesas,cpg-mstp-clocks"; -> >> + reg =3D <0 0xe615013c 0 4>, <0 0xe6150048 0 4>; -> >> + clocks =3D <&p_clk>; -> >> + #clock-cells =3D <1>; -> >> + renesas,clock-indices =3D <RCAR_GEN3_CLK_IRDA>; -> >> + clock-output-names =3D "irda"; +> >> + reg = <0 0xe615013c 0 4>, <0 0xe6150048 0 4>; +> >> + clocks = <&p_clk>; +> >> + #clock-cells = <1>; +> >> + renesas,clock-indices = <RCAR_GEN3_CLK_IRDA>; +> >> + clock-output-names = "irda"; > >> + }; > >> + }; > >> +}; -> = - +> > Gr{oetje,eeting}s, -> = - +> > Geert -> = - +> > -- -> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m6= -8k.org -> = - -> In personal conversations with technical people, I call myself a hacker. = -But -> when I'm talking to journalists I just say "programmer" or something like= - that. +> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org +> +> In personal conversations with technical people, I call myself a hacker. But +> when I'm talking to journalists I just say "programmer" or something like that. > -- Linus Torvalds > -- > To unsubscribe from this list: send the line "unsubscribe linux-clk" in diff --git a/a/content_digest b/N1/content_digest index b8ab8fa..efd542d 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -4,7 +4,7 @@ "ref\0CAMuHMdX+edyEWNaSV5d7Knxs8ZjxN7hLPqQgmb+4awNNnfpRDQ@mail.gmail.com\0" "From\0Michael Turquette <mturquette@baylibre.com>\0" "Subject\0Re: [PATCH 3/4 v3][RFC] arm64: renesas: Add initial r8a7795 SoC support\0" - "Date\0Mon, 17 Aug 2015 17:20:18 -0700\0" + "Date\0Tue, 18 Aug 2015 00:20:18 +0000\0" "To\0Geert Uytterhoeven <geert@linux-m68k.org>" " Laurent Pinchart <laurent.pinchart@ideasonboard.com>\0" "Cc\0Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>" @@ -23,35 +23,24 @@ "> >> +++ b/arch/arm64/boot/dts/renesas/r8a7795.dtsi\n" "> >> @@ -0,0 +1,93 @@\n" "> >> +/ {\n" - "> =\n" - "\n" + "> \n" "> >> + clocks {\n" "> >\n" - "> > Let's try to make it right from the start on Gen3. The CPG node should =\n" - "be a\n" - "> > direct child of the bus node mentioned above, and the MSTP clocks shoul=\n" - "d be\n" + "> > Let's try to make it right from the start on Gen3. The CPG node should be a\n" + "> > direct child of the bus node mentioned above, and the MSTP clocks should be\n" "> > children of the CPG node.\n" - "> =\n" - "\n" + "> \n" "> Agreed.\n" - "> =\n" - "\n" - "> > I'm not sure where to put the non-memory-mapped clocks though, should t=\n" - "hey be\n" - "> > directly under the root node ? It would make sense for extal_clk, but h=\n" - "ow\n" - "> > about the fixed-factor clocks ? Should they be children of the CPG node=\n" - " too ?\n" - "> =\n" - "\n" - "> I believe the current trend is to put clocks like \"extal_clk\" under the r=\n" - "oot\n" + "> \n" + "> > I'm not sure where to put the non-memory-mapped clocks though, should they be\n" + "> > directly under the root node ? It would make sense for extal_clk, but how\n" + "> > about the fixed-factor clocks ? Should they be children of the CPG node too ?\n" + "> \n" + "> I believe the current trend is to put clocks like \"extal_clk\" under the root\n" "> node.\n" "> As the fixed-factor clocks are generated by the CPG module, and we do have\n" "> a device node for it, I'd make them children of the CPG node, too.\n" - "> =\n" - "\n" + "> \n" "> Any comments from the clk+dt experts?\n" "\n" "I don't know if anyone is an expert ;-)\n" @@ -83,71 +72,61 @@ "Regards,\n" "Mike\n" "\n" - "> =\n" - "\n" + "> \n" "> Thanks!\n" - "> =\n" - "\n" - "> >> + #address-cells =3D <2>;\n" - "> >> + #size-cells =3D <2>;\n" + "> \n" + "> >> + #address-cells = <2>;\n" + "> >> + #size-cells = <2>;\n" "> >> + ranges;\n" "> >> +\n" "> >> + extal_clk: extal_clk {\n" - "> >> + compatible =3D \"fixed-clock\";\n" - "> >> + #clock-cells =3D <0>;\n" - "> >> + clock-frequency =3D <0>;\n" - "> >> + clock-output-names =3D \"extal\";\n" + "> >> + compatible = \"fixed-clock\";\n" + "> >> + #clock-cells = <0>;\n" + "> >> + clock-frequency = <0>;\n" + "> >> + clock-output-names = \"extal\";\n" "> >> + };\n" "> >> + cpg_clocks: cpg_clocks@e6150000 {\n" - "> >> + compatible =3D \"renesas,r8a7795-cpg-clocks\",\n" + "> >> + compatible = \"renesas,r8a7795-cpg-clocks\",\n" "> >> + \"renesas,rcar-gen3-cpg-clocks\";\n" - "> >> + reg =3D <0 0xe6150000 0 0x1000>;\n" - "> >> + clocks =3D <&extal_clk>;\n" - "> >> + #clock-cells =3D <1>;\n" - "> >> + clock-output-names =3D \"main\", \"pll0\", \"pll1\",\"p=\n" - "ll2\",\n" + "> >> + reg = <0 0xe6150000 0 0x1000>;\n" + "> >> + clocks = <&extal_clk>;\n" + "> >> + #clock-cells = <1>;\n" + "> >> + clock-output-names = \"main\", \"pll0\", \"pll1\",\"pll2\",\n" "> >> + \"pll3\", \"pll4\";\n" "> >> + };\n" "> >> + p_clk: p_clk {\n" - "> >> + compatible =3D \"fixed-factor-clock\";\n" - "> >> + clocks =3D <&cpg_clocks RCAR_GEN3_CLK_PLL1>;\n" - "> >> + #clock-cells =3D <0>;\n" - "> >> + clock-div =3D <24>;\n" - "> >> + clock-mult =3D <1>;\n" - "> >> + clock-output-names =3D \"p\";\n" + "> >> + compatible = \"fixed-factor-clock\";\n" + "> >> + clocks = <&cpg_clocks RCAR_GEN3_CLK_PLL1>;\n" + "> >> + #clock-cells = <0>;\n" + "> >> + clock-div = <24>;\n" + "> >> + clock-mult = <1>;\n" + "> >> + clock-output-names = \"p\";\n" "> >> + };\n" "> >> + mstp3_clks: mstp3_clks@e615013c {\n" - "> >> + compatible =3D \"renesas,r8a7795-mstp-clocks\",\n" + "> >> + compatible = \"renesas,r8a7795-mstp-clocks\",\n" "> >> + \"renesas,cpg-mstp-clocks\";\n" - "> >> + reg =3D <0 0xe615013c 0 4>, <0 0xe6150048 0 4>;\n" - "> >> + clocks =3D <&p_clk>;\n" - "> >> + #clock-cells =3D <1>;\n" - "> >> + renesas,clock-indices =3D <RCAR_GEN3_CLK_IRDA>;\n" - "> >> + clock-output-names =3D \"irda\";\n" + "> >> + reg = <0 0xe615013c 0 4>, <0 0xe6150048 0 4>;\n" + "> >> + clocks = <&p_clk>;\n" + "> >> + #clock-cells = <1>;\n" + "> >> + renesas,clock-indices = <RCAR_GEN3_CLK_IRDA>;\n" + "> >> + clock-output-names = \"irda\";\n" "> >> + };\n" "> >> + };\n" "> >> +};\n" - "> =\n" - "\n" + "> \n" "> Gr{oetje,eeting}s,\n" - "> =\n" - "\n" + "> \n" "> Geert\n" - "> =\n" - "\n" + "> \n" "> --\n" - "> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m6=\n" - "8k.org\n" - "> =\n" - "\n" - "> In personal conversations with technical people, I call myself a hacker. =\n" - "But\n" - "> when I'm talking to journalists I just say \"programmer\" or something like=\n" - " that.\n" + "> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org\n" + "> \n" + "> In personal conversations with technical people, I call myself a hacker. But\n" + "> when I'm talking to journalists I just say \"programmer\" or something like that.\n" "> -- Linus Torvalds\n" "> --\n" "> To unsubscribe from this list: send the line \"unsubscribe linux-clk\" in\n" "> the body of a message to majordomo@vger.kernel.org\n" > More majordomo info at http://vger.kernel.org/majordomo-info.html -7059a1a5a90cb6864d3cc3373ab47fb968ee5bb3319de4ec73e5ce79e86706bf +4e81d09b01240490fc1d51fa26d3ee32b728a544369ad2a29808a31df2db8bf3
diff --git a/a/1.txt b/N2/1.txt index 5c98ee8..6772812 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -6,35 +6,24 @@ Quoting Geert Uytterhoeven (2015-08-04 05:34:06) > >> +++ b/arch/arm64/boot/dts/renesas/r8a7795.dtsi > >> @@ -0,0 +1,93 @@ > >> +/ { -> = - +> > >> + clocks { > > -> > Let's try to make it right from the start on Gen3. The CPG node should = -be a -> > direct child of the bus node mentioned above, and the MSTP clocks shoul= -d be +> > Let's try to make it right from the start on Gen3. The CPG node should be a +> > direct child of the bus node mentioned above, and the MSTP clocks should be > > children of the CPG node. -> = - +> > Agreed. -> = - -> > I'm not sure where to put the non-memory-mapped clocks though, should t= -hey be -> > directly under the root node ? It would make sense for extal_clk, but h= -ow -> > about the fixed-factor clocks ? Should they be children of the CPG node= - too ? -> = - -> I believe the current trend is to put clocks like "extal_clk" under the r= -oot +> +> > I'm not sure where to put the non-memory-mapped clocks though, should they be +> > directly under the root node ? It would make sense for extal_clk, but how +> > about the fixed-factor clocks ? Should they be children of the CPG node too ? +> +> I believe the current trend is to put clocks like "extal_clk" under the root > node. > As the fixed-factor clocks are generated by the CPG module, and we do have > a device node for it, I'd make them children of the CPG node, too. -> = - +> > Any comments from the clk+dt experts? I don't know if anyone is an expert ;-) @@ -66,67 +55,57 @@ expressing your clock data with C inside of your provider driver. Regards, Mike -> = - +> > Thanks! -> = - -> >> + #address-cells =3D <2>; -> >> + #size-cells =3D <2>; +> +> >> + #address-cells = <2>; +> >> + #size-cells = <2>; > >> + ranges; > >> + > >> + extal_clk: extal_clk { -> >> + compatible =3D "fixed-clock"; -> >> + #clock-cells =3D <0>; -> >> + clock-frequency =3D <0>; -> >> + clock-output-names =3D "extal"; +> >> + compatible = "fixed-clock"; +> >> + #clock-cells = <0>; +> >> + clock-frequency = <0>; +> >> + clock-output-names = "extal"; > >> + }; > >> + cpg_clocks: cpg_clocks@e6150000 { -> >> + compatible =3D "renesas,r8a7795-cpg-clocks", +> >> + compatible = "renesas,r8a7795-cpg-clocks", > >> + "renesas,rcar-gen3-cpg-clocks"; -> >> + reg =3D <0 0xe6150000 0 0x1000>; -> >> + clocks =3D <&extal_clk>; -> >> + #clock-cells =3D <1>; -> >> + clock-output-names =3D "main", "pll0", "pll1","p= -ll2", +> >> + reg = <0 0xe6150000 0 0x1000>; +> >> + clocks = <&extal_clk>; +> >> + #clock-cells = <1>; +> >> + clock-output-names = "main", "pll0", "pll1","pll2", > >> + "pll3", "pll4"; > >> + }; > >> + p_clk: p_clk { -> >> + compatible =3D "fixed-factor-clock"; -> >> + clocks =3D <&cpg_clocks RCAR_GEN3_CLK_PLL1>; -> >> + #clock-cells =3D <0>; -> >> + clock-div =3D <24>; -> >> + clock-mult =3D <1>; -> >> + clock-output-names =3D "p"; +> >> + compatible = "fixed-factor-clock"; +> >> + clocks = <&cpg_clocks RCAR_GEN3_CLK_PLL1>; +> >> + #clock-cells = <0>; +> >> + clock-div = <24>; +> >> + clock-mult = <1>; +> >> + clock-output-names = "p"; > >> + }; > >> + mstp3_clks: mstp3_clks@e615013c { -> >> + compatible =3D "renesas,r8a7795-mstp-clocks", +> >> + compatible = "renesas,r8a7795-mstp-clocks", > >> + "renesas,cpg-mstp-clocks"; -> >> + reg =3D <0 0xe615013c 0 4>, <0 0xe6150048 0 4>; -> >> + clocks =3D <&p_clk>; -> >> + #clock-cells =3D <1>; -> >> + renesas,clock-indices =3D <RCAR_GEN3_CLK_IRDA>; -> >> + clock-output-names =3D "irda"; +> >> + reg = <0 0xe615013c 0 4>, <0 0xe6150048 0 4>; +> >> + clocks = <&p_clk>; +> >> + #clock-cells = <1>; +> >> + renesas,clock-indices = <RCAR_GEN3_CLK_IRDA>; +> >> + clock-output-names = "irda"; > >> + }; > >> + }; > >> +}; -> = - +> > Gr{oetje,eeting}s, -> = - +> > Geert -> = - +> > -- -> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m6= -8k.org -> = - -> In personal conversations with technical people, I call myself a hacker. = -But -> when I'm talking to journalists I just say "programmer" or something like= - that. +> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org +> +> In personal conversations with technical people, I call myself a hacker. But +> when I'm talking to journalists I just say "programmer" or something like that. > -- Linus Torvalds > -- > To unsubscribe from this list: send the line "unsubscribe linux-clk" in diff --git a/a/content_digest b/N2/content_digest index b8ab8fa..d3fa37c 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -23,35 +23,24 @@ "> >> +++ b/arch/arm64/boot/dts/renesas/r8a7795.dtsi\n" "> >> @@ -0,0 +1,93 @@\n" "> >> +/ {\n" - "> =\n" - "\n" + "> \n" "> >> + clocks {\n" "> >\n" - "> > Let's try to make it right from the start on Gen3. The CPG node should =\n" - "be a\n" - "> > direct child of the bus node mentioned above, and the MSTP clocks shoul=\n" - "d be\n" + "> > Let's try to make it right from the start on Gen3. The CPG node should be a\n" + "> > direct child of the bus node mentioned above, and the MSTP clocks should be\n" "> > children of the CPG node.\n" - "> =\n" - "\n" + "> \n" "> Agreed.\n" - "> =\n" - "\n" - "> > I'm not sure where to put the non-memory-mapped clocks though, should t=\n" - "hey be\n" - "> > directly under the root node ? It would make sense for extal_clk, but h=\n" - "ow\n" - "> > about the fixed-factor clocks ? Should they be children of the CPG node=\n" - " too ?\n" - "> =\n" - "\n" - "> I believe the current trend is to put clocks like \"extal_clk\" under the r=\n" - "oot\n" + "> \n" + "> > I'm not sure where to put the non-memory-mapped clocks though, should they be\n" + "> > directly under the root node ? It would make sense for extal_clk, but how\n" + "> > about the fixed-factor clocks ? Should they be children of the CPG node too ?\n" + "> \n" + "> I believe the current trend is to put clocks like \"extal_clk\" under the root\n" "> node.\n" "> As the fixed-factor clocks are generated by the CPG module, and we do have\n" "> a device node for it, I'd make them children of the CPG node, too.\n" - "> =\n" - "\n" + "> \n" "> Any comments from the clk+dt experts?\n" "\n" "I don't know if anyone is an expert ;-)\n" @@ -83,71 +72,61 @@ "Regards,\n" "Mike\n" "\n" - "> =\n" - "\n" + "> \n" "> Thanks!\n" - "> =\n" - "\n" - "> >> + #address-cells =3D <2>;\n" - "> >> + #size-cells =3D <2>;\n" + "> \n" + "> >> + #address-cells = <2>;\n" + "> >> + #size-cells = <2>;\n" "> >> + ranges;\n" "> >> +\n" "> >> + extal_clk: extal_clk {\n" - "> >> + compatible =3D \"fixed-clock\";\n" - "> >> + #clock-cells =3D <0>;\n" - "> >> + clock-frequency =3D <0>;\n" - "> >> + clock-output-names =3D \"extal\";\n" + "> >> + compatible = \"fixed-clock\";\n" + "> >> + #clock-cells = <0>;\n" + "> >> + clock-frequency = <0>;\n" + "> >> + clock-output-names = \"extal\";\n" "> >> + };\n" "> >> + cpg_clocks: cpg_clocks@e6150000 {\n" - "> >> + compatible =3D \"renesas,r8a7795-cpg-clocks\",\n" + "> >> + compatible = \"renesas,r8a7795-cpg-clocks\",\n" "> >> + \"renesas,rcar-gen3-cpg-clocks\";\n" - "> >> + reg =3D <0 0xe6150000 0 0x1000>;\n" - "> >> + clocks =3D <&extal_clk>;\n" - "> >> + #clock-cells =3D <1>;\n" - "> >> + clock-output-names =3D \"main\", \"pll0\", \"pll1\",\"p=\n" - "ll2\",\n" + "> >> + reg = <0 0xe6150000 0 0x1000>;\n" + "> >> + clocks = <&extal_clk>;\n" + "> >> + #clock-cells = <1>;\n" + "> >> + clock-output-names = \"main\", \"pll0\", \"pll1\",\"pll2\",\n" "> >> + \"pll3\", \"pll4\";\n" "> >> + };\n" "> >> + p_clk: p_clk {\n" - "> >> + compatible =3D \"fixed-factor-clock\";\n" - "> >> + clocks =3D <&cpg_clocks RCAR_GEN3_CLK_PLL1>;\n" - "> >> + #clock-cells =3D <0>;\n" - "> >> + clock-div =3D <24>;\n" - "> >> + clock-mult =3D <1>;\n" - "> >> + clock-output-names =3D \"p\";\n" + "> >> + compatible = \"fixed-factor-clock\";\n" + "> >> + clocks = <&cpg_clocks RCAR_GEN3_CLK_PLL1>;\n" + "> >> + #clock-cells = <0>;\n" + "> >> + clock-div = <24>;\n" + "> >> + clock-mult = <1>;\n" + "> >> + clock-output-names = \"p\";\n" "> >> + };\n" "> >> + mstp3_clks: mstp3_clks@e615013c {\n" - "> >> + compatible =3D \"renesas,r8a7795-mstp-clocks\",\n" + "> >> + compatible = \"renesas,r8a7795-mstp-clocks\",\n" "> >> + \"renesas,cpg-mstp-clocks\";\n" - "> >> + reg =3D <0 0xe615013c 0 4>, <0 0xe6150048 0 4>;\n" - "> >> + clocks =3D <&p_clk>;\n" - "> >> + #clock-cells =3D <1>;\n" - "> >> + renesas,clock-indices =3D <RCAR_GEN3_CLK_IRDA>;\n" - "> >> + clock-output-names =3D \"irda\";\n" + "> >> + reg = <0 0xe615013c 0 4>, <0 0xe6150048 0 4>;\n" + "> >> + clocks = <&p_clk>;\n" + "> >> + #clock-cells = <1>;\n" + "> >> + renesas,clock-indices = <RCAR_GEN3_CLK_IRDA>;\n" + "> >> + clock-output-names = \"irda\";\n" "> >> + };\n" "> >> + };\n" "> >> +};\n" - "> =\n" - "\n" + "> \n" "> Gr{oetje,eeting}s,\n" - "> =\n" - "\n" + "> \n" "> Geert\n" - "> =\n" - "\n" + "> \n" "> --\n" - "> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m6=\n" - "8k.org\n" - "> =\n" - "\n" - "> In personal conversations with technical people, I call myself a hacker. =\n" - "But\n" - "> when I'm talking to journalists I just say \"programmer\" or something like=\n" - " that.\n" + "> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org\n" + "> \n" + "> In personal conversations with technical people, I call myself a hacker. But\n" + "> when I'm talking to journalists I just say \"programmer\" or something like that.\n" "> -- Linus Torvalds\n" "> --\n" "> To unsubscribe from this list: send the line \"unsubscribe linux-clk\" in\n" "> the body of a message to majordomo@vger.kernel.org\n" > More majordomo info at http://vger.kernel.org/majordomo-info.html -7059a1a5a90cb6864d3cc3373ab47fb968ee5bb3319de4ec73e5ce79e86706bf +352baa29d3b459bfa208e1cd02f168cc99b5479e29a42206059541f2871c2d86
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.