* [GIT PULL] Device Tree fixes for v3.9
@ 2013-03-01 23:06 Linus Walleij
2013-03-01 23:19 ` Arnd Bergmann
2013-03-15 21:25 ` Arnd Bergmann
0 siblings, 2 replies; 10+ messages in thread
From: Linus Walleij @ 2013-03-01 23:06 UTC (permalink / raw)
To: linux-arm-kernel
Hi Olof, Arnd,
Here is a pull request for the Device Tree fixes for Ux500 in the v3.9 series.
Basically this should have come in earlier, but I failed at processing
it in time
for the merge window. t should have been this cycle's Ux500 DT topic branch.
As discussed I've started to funnel all Ux500 DT stuff through my ux500 tree
in order to do some coordination and I became overloaded. So this patch set
got stuck in the air. It was not trivial to push since this branch had a few
conflicts with other branches. (There might have been a good way to solve
that but I didn't come up with it in time.)
Basically how to handle it is your pick, in the old times I would have pushed
it ASAP, maybe during -rc1, as it restores the Ux500 DT to a working state
for the basic functionality (notably ethernet and MMC on the Snowball).
Please pull it in, for fixes or -next at your decision. As you can see the
base is at Torvald's HEAD since all dependencies that conflicted with
this branch is now there. If you want me to resend based on v3.9-rc1
or so, just tell.
Yours,
Linus Walleij
The following changes since commit b0af9cd9aab60ceb17d3ebabb9fdf4ff0a99cf50:
Merge tag 'lzo-update-signature-20130226' of
git://github.com/markus-oberhumer/linux (2013-02-28 20:45:52 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-stericsson.git
tags/ux500-dt-fixes
for you to fetch changes up to 924e82dacab9a0b2ea661c57c98112569267f0db:
ARM: ux500: allow Snowball access to the AB8500 GPIO pins
(2013-03-01 23:30:20 +0100)
----------------------------------------------------------------
Ux500 Device Tree fixes
All are necessary to make a proper DT boot on the v3.9
series:
- IRQ edges.
- Register defines.
- FSMC clock.
- Ethernet clk fixup (one patch to drivers/net ACKed by
David Miller)
- Proper IOS and regulator voltages for MMCI.
- AB8500 GPIOs restored after they were fixed in the v3.9
merge window from the pinctrl tree.
- There is also a minor cleanup in the platform code, but it
is strongly connected to the other patches.
----------------------------------------------------------------
Lee Jones (16):
ARM: ux500: Change IRQ from low-to-high edge triggered to high-to-low
ARM: ux500: Include the PRCMU's Secure Registers in DB8500's DT
ARM: ux500: Provide a means to obtain the SMSC9115 clock when DT
is enabled
clk: ux500: Ensure the FMSC clock is obtainable
clk: ux500: Provide an alias for the SMSC911x Ethernet chip
net/smsc911x: Provide common clock functionality
mmc: mmci: Move ios_handler functionality into the driver
ARM: ux500: Set correct MMCI regulator voltages in the ux5x0 Device Tree
ARM: ux500: Specify the ux5x0 MMCI regulator's on/off GPIO as high-enable
ARM: ux500: Specify which IOS regulator to use for MMCI
ARM: ux500: Use the correct name when supplying a GPIO enable pin
ARM: ux500: Setup correct settling time for the MMCI regulator
ARM: ux500: Use the GPIO regulator framework for SDI0's 'en' and 'vsel'
ARM: ux500: Remove traces of the ios_handler from platform code
ARM: ux500: enable AB8500 GPIO for HREF
ARM: ux500: allow Snowball access to the AB8500 GPIO pins
arch/arm/boot/dts/dbx5x0.dtsi | 7 ++--
arch/arm/boot/dts/href.dtsi | 1 +
arch/arm/boot/dts/hrefprev60.dts | 10 +++++-
arch/arm/boot/dts/snowball.dts | 4 +++
arch/arm/boot/dts/stuib.dtsi | 2 +-
arch/arm/mach-ux500/board-mop500-regulators.c | 14 ++++++++
arch/arm/mach-ux500/board-mop500-regulators.h | 1 +
arch/arm/mach-ux500/board-mop500-sdi.c | 52 ---------------------------
arch/arm/mach-ux500/board-mop500.c | 45 +++++++++++++++++++++++
arch/arm/mach-ux500/cpu-db8500.c | 1 +
drivers/clk/ux500/u8500_clk.c | 3 +-
drivers/mmc/host/mmci.c | 9 +++++
drivers/net/ethernet/smsc/smsc911x.c | 29 ++++++++++++++-
13 files changed, 120 insertions(+), 58 deletions(-)
^ permalink raw reply [flat|nested] 10+ messages in thread* [GIT PULL] Device Tree fixes for v3.9 2013-03-01 23:06 [GIT PULL] Device Tree fixes for v3.9 Linus Walleij @ 2013-03-01 23:19 ` Arnd Bergmann 2013-03-02 0:58 ` Lee Jones 2013-03-15 21:25 ` Arnd Bergmann 1 sibling, 1 reply; 10+ messages in thread From: Arnd Bergmann @ 2013-03-01 23:19 UTC (permalink / raw) To: linux-arm-kernel On Friday 01 March 2013, Linus Walleij wrote: > Hi Olof, Arnd, > > Here is a pull request for the Device Tree fixes for Ux500 in the v3.9 series. > > Basically this should have come in earlier, but I failed at processing > it in time > for the merge window. t should have been this cycle's Ux500 DT topic branch. > > As discussed I've started to funnel all Ux500 DT stuff through my ux500 tree > in order to do some coordination and I became overloaded. So this patch set > got stuck in the air. It was not trivial to push since this branch had a few > conflicts with other branches. (There might have been a good way to solve > that but I didn't come up with it in time.) > > Basically how to handle it is your pick, in the old times I would have pushed > it ASAP, maybe during -rc1, as it restores the Ux500 DT to a working state > for the basic functionality (notably ethernet and MMC on the Snowball). > > Please pull it in, for fixes or -next at your decision. As you can see the > base is at Torvald's HEAD since all dependencies that conflicted with > this branch is now there. If you want me to resend based on v3.9-rc1 > or so, just tell. I'm still getting build errors even with those patches applied: Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1) Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1) Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1) Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1) drivers/built-in.o: In function `ab8500_power_off': /git/arm-soc/drivers/mfd/ab8500-sysctrl.c:37: undefined reference to `power_supply_get_by_name' /git/arm-soc/drivers/mfd/ab8500-sysctrl.c:53: undefined reference to `power_supply_get_by_name' make[2]: *** [vmlinux] Error 1 Arnd 1 ` ^ permalink raw reply [flat|nested] 10+ messages in thread
* [GIT PULL] Device Tree fixes for v3.9 2013-03-01 23:19 ` Arnd Bergmann @ 2013-03-02 0:58 ` Lee Jones 2013-03-11 14:43 ` Arnd Bergmann 0 siblings, 1 reply; 10+ messages in thread From: Lee Jones @ 2013-03-02 0:58 UTC (permalink / raw) To: linux-arm-kernel On Fri, 01 Mar 2013, Arnd Bergmann wrote: > On Friday 01 March 2013, Linus Walleij wrote: > > Hi Olof, Arnd, > > > > Here is a pull request for the Device Tree fixes for Ux500 in the v3.9 series. > > > > Basically this should have come in earlier, but I failed at processing > > it in time > > for the merge window. t should have been this cycle's Ux500 DT topic branch. > > > > As discussed I've started to funnel all Ux500 DT stuff through my ux500 tree > > in order to do some coordination and I became overloaded. So this patch set > > got stuck in the air. It was not trivial to push since this branch had a few > > conflicts with other branches. (There might have been a good way to solve > > that but I didn't come up with it in time.) > > > > Basically how to handle it is your pick, in the old times I would have pushed > > it ASAP, maybe during -rc1, as it restores the Ux500 DT to a working state > > for the basic functionality (notably ethernet and MMC on the Snowball). > > > > Please pull it in, for fixes or -next at your decision. As you can see the > > base is at Torvald's HEAD since all dependencies that conflicted with > > this branch is now there. If you want me to resend based on v3.9-rc1 > > or so, just tell. > > > I'm still getting build errors even with those patches applied: > > Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1) > Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1) > Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1) > Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1) These have been there since DT landed for the AB8500 - it's on my TODO to fix, but it's a really low priority. > drivers/built-in.o: In function `ab8500_power_off': > /git/arm-soc/drivers/mfd/ab8500-sysctrl.c:37: undefined reference to `power_supply_get_by_name' > /git/arm-soc/drivers/mfd/ab8500-sysctrl.c:53: undefined reference to `power_supply_get_by_name' > make[2]: *** [vmlinux] Error 1 This has already been fixed. https://patchwork.kernel.org/patch/2163301/ -- Lee Jones Linaro ST-Ericsson Landing Team Lead Linaro.org ? Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog ^ permalink raw reply [flat|nested] 10+ messages in thread
* [GIT PULL] Device Tree fixes for v3.9 2013-03-02 0:58 ` Lee Jones @ 2013-03-11 14:43 ` Arnd Bergmann 2013-03-11 14:51 ` Samuel Ortiz 2013-03-13 8:37 ` Samuel Ortiz 0 siblings, 2 replies; 10+ messages in thread From: Arnd Bergmann @ 2013-03-11 14:43 UTC (permalink / raw) To: linux-arm-kernel On Saturday 02 March 2013, Lee Jones wrote: > > > > I'm still getting build errors even with those patches applied: > > > > Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1) > > Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1) > > Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1) > > Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1) > > These have been there since DT landed for the AB8500 - it's on my TODO > to fix, but it's a really low priority. I've come up with the trivial patch below. I'm trying hard to kill off all known warnings, and will not take submissions introducing new ones if I see them. Maybe Sam can just pick this up along with the other patch. > > drivers/built-in.o: In function `ab8500_power_off': > > /git/arm-soc/drivers/mfd/ab8500-sysctrl.c:37: undefined reference to `power_supply_get_by_name' > > /git/arm-soc/drivers/mfd/ab8500-sysctrl.c:53: undefined reference to `power_supply_get_by_name' > > make[2]: *** [vmlinux] Error 1 > > This has already been fixed. > > https://patchwork.kernel.org/patch/2163301/ It hasn't made it into v3.9-rc2 or even linux-next yet. I guess it got lost somewhere. Arnd 8<--------- Subject: mfd: ab8500: kill "reg" property from binding The ab8500 device is a child of the prcmu device, which is a memory mapped bus device, whose children are addressable using physical memory addresses, not using mailboxes, so a mailbox number in the ab8500 node cannot be parsed by DT. Nothing uses this number, since it was only introduced as part of the failed attempt to clean up prcmu mailbox handling, and we can simply remove it. Signed-off-by: Arnd Bergmann <arnd@arndb.de> diff --git a/Documentation/devicetree/bindings/mfd/ab8500.txt b/Documentation/devicetree/bindings/mfd/ab8500.txt index 13b707b..c3a14e0 100644 --- a/Documentation/devicetree/bindings/mfd/ab8500.txt +++ b/Documentation/devicetree/bindings/mfd/ab8500.txt @@ -13,9 +13,6 @@ Required parent device properties: 4 = active high level-sensitive 8 = active low level-sensitive -Optional parent device properties: -- reg : contains the PRCMU mailbox address for the AB8500 i2c port - The AB8500 consists of a large and varied group of sub-devices: Device IRQ Names Supply Names Description @@ -86,9 +83,8 @@ Non-standard child device properties: - stericsson,amic2-bias-vamic1 : Analoge Mic wishes to use a non-standard Vamic - stericsson,earpeice-cmv : Earpeice voltage (only: 950 | 1100 | 1270 | 1580) -ab8500 at 5 { +ab8500 { compatible = "stericsson,ab8500"; - reg = <5>; /* mailbox 5 is i2c */ interrupts = <0 40 0x4>; interrupt-controller; #interrupt-cells = <2>; diff --git a/arch/arm/boot/dts/dbx5x0.dtsi b/arch/arm/boot/dts/dbx5x0.dtsi index 69140ba..9de9309 100644 --- a/arch/arm/boot/dts/dbx5x0.dtsi +++ b/arch/arm/boot/dts/dbx5x0.dtsi @@ -319,9 +319,8 @@ }; }; - ab8500 at 5 { + ab8500 { compatible = "stericsson,ab8500"; - reg = <5>; /* mailbox 5 is i2c */ interrupt-parent = <&intc>; interrupts = <0 40 0x4>; interrupt-controller; diff --git a/arch/arm/boot/dts/href.dtsi b/arch/arm/boot/dts/href.dtsi index 592fb9d..379128e 100644 --- a/arch/arm/boot/dts/href.dtsi +++ b/arch/arm/boot/dts/href.dtsi @@ -221,7 +221,7 @@ }; }; - ab8500 at 5 { + ab8500 { ab8500-regulators { ab8500_ldo_aux1_reg: ab8500_ldo_aux1 { regulator-name = "V-DISPLAY"; diff --git a/arch/arm/boot/dts/hrefv60plus.dts b/arch/arm/boot/dts/hrefv60plus.dts index 55f4191..2b587a7 100644 --- a/arch/arm/boot/dts/hrefv60plus.dts +++ b/arch/arm/boot/dts/hrefv60plus.dts @@ -158,7 +158,7 @@ }; }; - ab8500 at 5 { + ab8500 { ab8500-regulators { ab8500_ldo_aux1_reg: ab8500_ldo_aux1 { regulator-name = "V-DISPLAY"; diff --git a/arch/arm/boot/dts/snowball.dts b/arch/arm/boot/dts/snowball.dts index 27f31a5..d3ec32f 100644 --- a/arch/arm/boot/dts/snowball.dts +++ b/arch/arm/boot/dts/snowball.dts @@ -298,7 +298,7 @@ }; }; - ab8500 at 5 { + ab8500 { ab8500-regulators { ab8500_ldo_aux1_reg: ab8500_ldo_aux1 { regulator-name = "V-DISPLAY"; ^ permalink raw reply related [flat|nested] 10+ messages in thread
* [GIT PULL] Device Tree fixes for v3.9 2013-03-11 14:43 ` Arnd Bergmann @ 2013-03-11 14:51 ` Samuel Ortiz 2013-03-11 15:20 ` Arnd Bergmann 2013-03-13 8:37 ` Samuel Ortiz 1 sibling, 1 reply; 10+ messages in thread From: Samuel Ortiz @ 2013-03-11 14:51 UTC (permalink / raw) To: linux-arm-kernel Hi Arnd, On Mon, Mar 11, 2013 at 02:43:20PM +0000, Arnd Bergmann wrote: > On Saturday 02 March 2013, Lee Jones wrote: > > > > > > I'm still getting build errors even with those patches applied: > > > > > > Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1) > > > Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1) > > > Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1) > > > Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1) > > > > These have been there since DT landed for the AB8500 - it's on my TODO > > to fix, but it's a really low priority. > > I've come up with the trivial patch below. I'm trying hard to kill off all known > warnings, and will not take submissions introducing new ones if I see them. > > Maybe Sam can just pick this up along with the other patch. I'll take it. > > > drivers/built-in.o: In function `ab8500_power_off': > > > /git/arm-soc/drivers/mfd/ab8500-sysctrl.c:37: undefined reference to `power_supply_get_by_name' > > > /git/arm-soc/drivers/mfd/ab8500-sysctrl.c:53: undefined reference to `power_supply_get_by_name' > > > make[2]: *** [vmlinux] Error 1 > > > > This has already been fixed. > > > > https://patchwork.kernel.org/patch/2163301/ > > It hasn't made it into v3.9-rc2 or even linux-next yet. I guess it got lost > somewhere. In my Inbox. I'm planning to send a pull request to Linus later this week. Cheers, Samuel. -- Intel Open Source Technology Centre http://oss.intel.com/ ^ permalink raw reply [flat|nested] 10+ messages in thread
* [GIT PULL] Device Tree fixes for v3.9 2013-03-11 14:51 ` Samuel Ortiz @ 2013-03-11 15:20 ` Arnd Bergmann 0 siblings, 0 replies; 10+ messages in thread From: Arnd Bergmann @ 2013-03-11 15:20 UTC (permalink / raw) To: linux-arm-kernel On Monday 11 March 2013, Samuel Ortiz wrote: > > Maybe Sam can just pick this up along with the other patch. > I'll take it. > ... > > It hasn't made it into v3.9-rc2 or even linux-next yet. I guess it got lost > > somewhere. > In my Inbox. I'm planning to send a pull request to Linus later this week. Ok, thanks a lot! Coincidentally, I just found another regression with an unrelated driver that got merged through your tree (max8925), I'll follow up with a separate email. Arnd ^ permalink raw reply [flat|nested] 10+ messages in thread
* [GIT PULL] Device Tree fixes for v3.9 2013-03-11 14:43 ` Arnd Bergmann 2013-03-11 14:51 ` Samuel Ortiz @ 2013-03-13 8:37 ` Samuel Ortiz 2013-03-13 18:01 ` Arnd Bergmann 1 sibling, 1 reply; 10+ messages in thread From: Samuel Ortiz @ 2013-03-13 8:37 UTC (permalink / raw) To: linux-arm-kernel Hi Arnd, On Mon, Mar 11, 2013 at 02:43:20PM +0000, Arnd Bergmann wrote: > On Saturday 02 March 2013, Lee Jones wrote: > > > > > > I'm still getting build errors even with those patches applied: > > > > > > Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1) > > > Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1) > > > Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1) > > > Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1) > > > > These have been there since DT landed for the AB8500 - it's on my TODO > > to fix, but it's a really low priority. > > I've come up with the trivial patch below. I'm trying hard to kill off all known > warnings, and will not take submissions introducing new ones if I see them. > > Maybe Sam can just pick this up along with the other patch. I applied the patch below to my fd-fixes tree. Which one do you mean by "the other patch" ? > > > drivers/built-in.o: In function `ab8500_power_off': > > > /git/arm-soc/drivers/mfd/ab8500-sysctrl.c:37: undefined reference to `power_supply_get_by_name' > > > /git/arm-soc/drivers/mfd/ab8500-sysctrl.c:53: undefined reference to `power_supply_get_by_name' > > > make[2]: *** [vmlinux] Error 1 > > > > This has already been fixed. > > > > https://patchwork.kernel.org/patch/2163301/ > > It hasn't made it into v3.9-rc2 or even linux-next yet. I guess it got lost > somewhere. It's applied to my mfd-fixes as well now. Cheers, Samuel. -- Intel Open Source Technology Centre http://oss.intel.com/ ^ permalink raw reply [flat|nested] 10+ messages in thread
* [GIT PULL] Device Tree fixes for v3.9 2013-03-13 8:37 ` Samuel Ortiz @ 2013-03-13 18:01 ` Arnd Bergmann 0 siblings, 0 replies; 10+ messages in thread From: Arnd Bergmann @ 2013-03-13 18:01 UTC (permalink / raw) To: linux-arm-kernel On Wednesday 13 March 2013, Samuel Ortiz wrote: > > Maybe Sam can just pick this up along with the other patch. > I applied the patch below to my fd-fixes tree. Which one do you mean by "the > other patch" ? The one that you said is in your tree below. > > > https://patchwork.kernel.org/patch/2163301/ > > > > It hasn't made it into v3.9-rc2 or even linux-next yet. I guess it got lost > > somewhere. > It's applied to my mfd-fixes as well now. Arnd ^ permalink raw reply [flat|nested] 10+ messages in thread
* [GIT PULL] Device Tree fixes for v3.9 2013-03-01 23:06 [GIT PULL] Device Tree fixes for v3.9 Linus Walleij 2013-03-01 23:19 ` Arnd Bergmann @ 2013-03-15 21:25 ` Arnd Bergmann 2013-03-15 22:18 ` Arnd Bergmann 1 sibling, 1 reply; 10+ messages in thread From: Arnd Bergmann @ 2013-03-15 21:25 UTC (permalink / raw) To: linux-arm-kernel On Friday 01 March 2013, Linus Walleij wrote: > Please pull it in, for fixes or -next at your decision. As you can see the > base is at Torvald's HEAD since all dependencies that conflicted with > this branch is now there. If you want me to resend based on v3.9-rc1 > or so, just tell. I guess it's too late not for 3.9, I just found the pull request again. I've applied it to the 3.10 next/fixes-non-critical branch now. Arnd ^ permalink raw reply [flat|nested] 10+ messages in thread
* [GIT PULL] Device Tree fixes for v3.9 2013-03-15 21:25 ` Arnd Bergmann @ 2013-03-15 22:18 ` Arnd Bergmann 0 siblings, 0 replies; 10+ messages in thread From: Arnd Bergmann @ 2013-03-15 22:18 UTC (permalink / raw) To: linux-arm-kernel On Friday 15 March 2013, Arnd Bergmann wrote: > I guess it's too late not for 3.9, I just found the pull request again. > I've applied it to the 3.10 next/fixes-non-critical branch now. > s/not/now/ Sorry for any confusion I caused. Arnd ^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2013-03-15 22:18 UTC | newest] Thread overview: 10+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2013-03-01 23:06 [GIT PULL] Device Tree fixes for v3.9 Linus Walleij 2013-03-01 23:19 ` Arnd Bergmann 2013-03-02 0:58 ` Lee Jones 2013-03-11 14:43 ` Arnd Bergmann 2013-03-11 14:51 ` Samuel Ortiz 2013-03-11 15:20 ` Arnd Bergmann 2013-03-13 8:37 ` Samuel Ortiz 2013-03-13 18:01 ` Arnd Bergmann 2013-03-15 21:25 ` Arnd Bergmann 2013-03-15 22:18 ` Arnd Bergmann
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).