* [GIT PULL] MMC fixes for v.4.12 rc3 - take 2/2
@ 2017-05-26 13:08 Ulf Hansson
2017-05-26 16:24 ` Olof Johansson
0 siblings, 1 reply; 6+ messages in thread
From: Ulf Hansson @ 2017-05-26 13:08 UTC (permalink / raw)
To: Linus, linux-mmc, linux-kernel@vger.kernel.org
Cc: arm@kernel.org, Arnd Bergmann
Hi Linus,
Here are a couple of mmc and arm64-dts fixes intended for v4.12 rc3.
They are based on v4.12-rc2.
Details are as usual found in the signed tag. Please pull this in!
Kind regards
Ulf Hansson
The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d:
Linux 4.12-rc2 (2017-05-21 19:30:23 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git tags/mmc-v4.12-rc2
for you to fetch changes up to ea452678734eb782126f999bf5c4fb3e71d3b196:
arm64: dts: hikey: Fix WiFi support (2017-05-23 14:18:10 +0200)
----------------------------------------------------------------
This pull request contains fixes to make the WiFi work again for the ARM64
Hikey board. Together with a couple of DTS updates for the Hikey board we have
also extended the mmc pwrseq_simple, to support a new power-off-delay-us DT
property, as that was required to enable a graceful power off sequence for the
WiFi chip.
----------------------------------------------------------------
Daniel Lezcano (2):
mfd: dts: hi655x: Add clock binding for the pmic
arm64: dts: hikey: Add clock for the pmic mfd
Ulf Hansson (6):
mmc: dt: pwrseq-simple: Invent power-off-delay-us
mmc: pwrseq_simple: Parse DTS for the power-off-delay-us property
arm64: dts: hi6220: Move the fixed_5v_hub regulator to the hikey dts
arm64: dts: hikey: Add the SYS_5V and the VDD_3V3 regulators
arm64: dts: hi6220: Move board data from the dwmmc nodes to hikey dts
arm64: dts: hikey: Fix WiFi support
.../devicetree/bindings/mfd/hisilicon,hi655x.txt | 6 ++
.../devicetree/bindings/mmc/mmc-pwrseq-simple.txt | 2 +
arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts | 78 +++++++++++++++++-----
arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 31 +--------
drivers/mmc/core/pwrseq_simple.c | 7 ++
5 files changed, 79 insertions(+), 45 deletions(-)
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [GIT PULL] MMC fixes for v.4.12 rc3 - take 2/2 2017-05-26 13:08 [GIT PULL] MMC fixes for v.4.12 rc3 - take 2/2 Ulf Hansson @ 2017-05-26 16:24 ` Olof Johansson 2017-05-28 10:26 ` Ulf Hansson 0 siblings, 1 reply; 6+ messages in thread From: Olof Johansson @ 2017-05-26 16:24 UTC (permalink / raw) To: Ulf Hansson Cc: Linus, linux-mmc, linux-kernel@vger.kernel.org, arm@kernel.org, Arnd Bergmann Hi Ulf, On Fri, May 26, 2017 at 6:08 AM, Ulf Hansson <ulf.hansson@linaro.org> wrote: > Hi Linus, > > Here are a couple of mmc and arm64-dts fixes intended for v4.12 rc3. > They are based on v4.12-rc2. > > Details are as usual found in the signed tag. Please pull this in! > > Kind regards > Ulf Hansson > > > The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d: > > Linux 4.12-rc2 (2017-05-21 19:30:23 -0700) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git tags/mmc-v4.12-rc2 > > for you to fetch changes up to ea452678734eb782126f999bf5c4fb3e71d3b196: > > arm64: dts: hikey: Fix WiFi support (2017-05-23 14:18:10 +0200) > > ---------------------------------------------------------------- > This pull request contains fixes to make the WiFi work again for the ARM64 > Hikey board. Together with a couple of DTS updates for the Hikey board we have > also extended the mmc pwrseq_simple, to support a new power-off-delay-us DT > property, as that was required to enable a graceful power off sequence for the > WiFi chip. > > ---------------------------------------------------------------- > Daniel Lezcano (2): > mfd: dts: hi655x: Add clock binding for the pmic > arm64: dts: hikey: Add clock for the pmic mfd > > Ulf Hansson (6): > mmc: dt: pwrseq-simple: Invent power-off-delay-us > mmc: pwrseq_simple: Parse DTS for the power-off-delay-us property > arm64: dts: hi6220: Move the fixed_5v_hub regulator to the hikey dts > arm64: dts: hikey: Add the SYS_5V and the VDD_3V3 regulators > arm64: dts: hi6220: Move board data from the dwmmc nodes to hikey dts > arm64: dts: hikey: Fix WiFi support These are a lot of changes to fix a regression. How was it introduced? It would also have been useful if you pointed out the DT contents was already acked by Arnd (I had to go look at the contents since you only looped him in, and no other ARM-SoC maintainers). -Olof ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [GIT PULL] MMC fixes for v.4.12 rc3 - take 2/2 2017-05-26 16:24 ` Olof Johansson @ 2017-05-28 10:26 ` Ulf Hansson 2017-05-29 10:22 ` Daniel Lezcano 0 siblings, 1 reply; 6+ messages in thread From: Ulf Hansson @ 2017-05-28 10:26 UTC (permalink / raw) To: Olof Johansson Cc: Linus, linux-mmc, linux-kernel@vger.kernel.org, arm@kernel.org, Arnd Bergmann, Daniel Lezcano Hi Olof, +Daniel On 26 May 2017 at 18:24, Olof Johansson <olof@lixom.net> wrote: > Hi Ulf, > > > On Fri, May 26, 2017 at 6:08 AM, Ulf Hansson <ulf.hansson@linaro.org> wrote: >> Hi Linus, >> >> Here are a couple of mmc and arm64-dts fixes intended for v4.12 rc3. >> They are based on v4.12-rc2. >> >> Details are as usual found in the signed tag. Please pull this in! >> >> Kind regards >> Ulf Hansson >> >> >> The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d: >> >> Linux 4.12-rc2 (2017-05-21 19:30:23 -0700) >> >> are available in the git repository at: >> >> git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git tags/mmc-v4.12-rc2 >> >> for you to fetch changes up to ea452678734eb782126f999bf5c4fb3e71d3b196: >> >> arm64: dts: hikey: Fix WiFi support (2017-05-23 14:18:10 +0200) >> >> ---------------------------------------------------------------- >> This pull request contains fixes to make the WiFi work again for the ARM64 >> Hikey board. Together with a couple of DTS updates for the Hikey board we have >> also extended the mmc pwrseq_simple, to support a new power-off-delay-us DT >> property, as that was required to enable a graceful power off sequence for the >> WiFi chip. >> >> ---------------------------------------------------------------- >> Daniel Lezcano (2): >> mfd: dts: hi655x: Add clock binding for the pmic >> arm64: dts: hikey: Add clock for the pmic mfd >> >> Ulf Hansson (6): >> mmc: dt: pwrseq-simple: Invent power-off-delay-us >> mmc: pwrseq_simple: Parse DTS for the power-off-delay-us property >> arm64: dts: hi6220: Move the fixed_5v_hub regulator to the hikey dts >> arm64: dts: hikey: Add the SYS_5V and the VDD_3V3 regulators >> arm64: dts: hi6220: Move board data from the dwmmc nodes to hikey dts >> arm64: dts: hikey: Fix WiFi support > > > These are a lot of changes to fix a regression. How was it introduced? It was several releases ago it got broken, exactly which one I can't really tell. I suspect this also is related to an upgrade of the boot loader, as in the earlier version of the series there where a pmic clock driver included, however it got picked up for 4.12. Looping in Daniel, just to see if he have some comments on this. No matter what, I still think it makes sense to pick this for 4.12 rcs, because it also simplifies for us for how to deal with the mmc+arm64 dependency, since this needs to go together (to avoid damaging the WiFi chip when power off) > > It would also have been useful if you pointed out the DT contents was > already acked by Arnd (I had to go look at the contents since you only > looped him in, and no other ARM-SoC maintainers). > Apologize about that! I will make that clear, if/when next time! > > -Olof Kind regards Uffe ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [GIT PULL] MMC fixes for v.4.12 rc3 - take 2/2 2017-05-28 10:26 ` Ulf Hansson @ 2017-05-29 10:22 ` Daniel Lezcano 2017-06-02 0:05 ` Olof Johansson 0 siblings, 1 reply; 6+ messages in thread From: Daniel Lezcano @ 2017-05-29 10:22 UTC (permalink / raw) To: Ulf Hansson Cc: Olof Johansson, Linus, linux-mmc, linux-kernel@vger.kernel.org, arm@kernel.org, Arnd Bergmann On Sun, May 28, 2017 at 12:26:00PM +0200, Ulf Hansson wrote: > Hi Olof, > > +Daniel > > On 26 May 2017 at 18:24, Olof Johansson <olof@lixom.net> wrote: > > Hi Ulf, > > > > > > On Fri, May 26, 2017 at 6:08 AM, Ulf Hansson <ulf.hansson@linaro.org> wrote: > >> Hi Linus, > >> > >> Here are a couple of mmc and arm64-dts fixes intended for v4.12 rc3. > >> They are based on v4.12-rc2. > >> > >> Details are as usual found in the signed tag. Please pull this in! > >> > >> Kind regards > >> Ulf Hansson > >> > >> > >> The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d: > >> > >> Linux 4.12-rc2 (2017-05-21 19:30:23 -0700) > >> > >> are available in the git repository at: > >> > >> git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git tags/mmc-v4.12-rc2 > >> > >> for you to fetch changes up to ea452678734eb782126f999bf5c4fb3e71d3b196: > >> > >> arm64: dts: hikey: Fix WiFi support (2017-05-23 14:18:10 +0200) > >> > >> ---------------------------------------------------------------- > >> This pull request contains fixes to make the WiFi work again for the ARM64 > >> Hikey board. Together with a couple of DTS updates for the Hikey board we have > >> also extended the mmc pwrseq_simple, to support a new power-off-delay-us DT > >> property, as that was required to enable a graceful power off sequence for the > >> WiFi chip. > >> > >> ---------------------------------------------------------------- > >> Daniel Lezcano (2): > >> mfd: dts: hi655x: Add clock binding for the pmic > >> arm64: dts: hikey: Add clock for the pmic mfd > >> > >> Ulf Hansson (6): > >> mmc: dt: pwrseq-simple: Invent power-off-delay-us > >> mmc: pwrseq_simple: Parse DTS for the power-off-delay-us property > >> arm64: dts: hi6220: Move the fixed_5v_hub regulator to the hikey dts > >> arm64: dts: hikey: Add the SYS_5V and the VDD_3V3 regulators > >> arm64: dts: hi6220: Move board data from the dwmmc nodes to hikey dts > >> arm64: dts: hikey: Fix WiFi support > > > > > > These are a lot of changes to fix a regression. How was it introduced? > > It was several releases ago it got broken, exactly which one I can't > really tell. > > I suspect this also is related to an upgrade of the boot loader, as in > the earlier version of the series there where a pmic clock driver > included, however it got picked up for 4.12. > > Looping in Daniel, just to see if he have some comments on this. Depending on the version of the bootloader, the sdio/mmc2 was not correctly set up and raised a hung task warning. This one has been fixed with the commit: commit 0fbdf9953b41c28845fe8d05007ff09634ee3000 Author: Daniel Lezcano <daniel.lezcano@linaro.org> Date: Thu Mar 16 15:03:24 2017 +0100 arm64: dts: hi6220: Reset the mmc hosts The MMC hosts could be left in an unconsistent or uninitialized state from the firmware. Instead of assuming, the firmware did the right things, let's reset the host controllers. This change fixes a bug when the mmc2/sdio is initialized leading to a hung task: [ 242.704294] INFO: task kworker/7:1:675 blocked for more than 120 seconds. [ 242.711129] Not tainted 4.9.0-rc8-00017-gcf0251f #3 [ 242.716571] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.724435] kworker/7:1 D 0 675 2 0x00000000 [ 242.729973] Workqueue: events_freezable mmc_rescan [ 242.734796] Call trace: [ 242.737269] [<ffff00000808611c>] __switch_to+0xa8/0xb4 [ 242.742437] [<ffff000008d07c04>] __schedule+0x1c0/0x67c [ 242.747689] [<ffff000008d08254>] schedule+0x40/0xa0 [ 242.752594] [<ffff000008d0b284>] schedule_timeout+0x1c4/0x35c [ 242.758366] [<ffff000008d08e38>] wait_for_common+0xd0/0x15c [ 242.763964] [<ffff000008d09008>] wait_for_completion+0x28/0x34 [ 242.769825] [<ffff000008a1a9f4>] mmc_wait_for_req_done+0x40/0x124 [ 242.775949] [<ffff000008a1ab98>] mmc_wait_for_req+0xc0/0xf8 [ 242.781549] [<ffff000008a1ac3c>] mmc_wait_for_cmd+0x6c/0x84 [ 242.787149] [<ffff000008a26610>] mmc_io_rw_direct_host+0x9c/0x114 [ 242.793270] [<ffff000008a26aa0>] sdio_reset+0x34/0x7c [ 242.798347] [<ffff000008a1d46c>] mmc_rescan+0x2fc/0x360 [ ... ] For the story, this mmc/sdio is for the WiFi and this one was working for some version of the bootloader which initialized the clock and set the enable line for the chip. That is bad because the WiFi is working as a side effect from the boot loader. In order to properly make support for the WiFi in the kernel, we need to sort out this by: - Reset the mmc - Implement the clock at the pmic level - Add the mfd clock cell - Add the DT definition The three first patches are merged, the first commit is described above, then we have: ------------------------------------------------------------------------------ commit ac03fec1d7d889192cce35edac6fef6026a4d6a1 Author: Daniel Lezcano <daniel.lezcano@linaro.org> Date: Fri Mar 17 08:58:50 2017 +0100 mfd: hi655x: Add the clock cell to provide WiFi and Bluetooth The hi655x is a PMIC with regulator but also provides a clock for the WiFi and the bluetooth which is missing in the current implementation. Add the clock cell so it can be used in the next patch via the dts. ------------------------------------------------------------------------------ commit b68adc23bc3d0c81a08b69cf1ba0bf0405c9d868 Author: Daniel Lezcano <daniel.lezcano@linaro.org> Date: Mon Apr 17 19:19:25 2017 +0200 clk: hi6220: Add the hi655x's pmic clock The hi655x multi function device is a PMIC providing regulators. The PMIC also provides a clock for the WiFi and the Bluetooth, let's implement this clock in order to add it in the hi655x MFD and allow proper wireless initialization. ------------------------------------------------------------------------------ The fourth patch was missed somehow and Ulf recaugth it in its series. Why? The wl18xx documentation tells if the enable line is set *before* the clock, that may damage the chip. By taking the series, we make sure the patches are in the right order (clock followed by the enable line with a delay in between as specified in the documentation). That said, I don't have a strong opinion on which version this series should go. The latest wl18xx driver version needs an update of the firmware, I'm not sure it is a good a idea to enable the WiFi in -rc as every hi6220 users will have to upgrade their firmware, on the other side it is not really a big deal. -- Daniel > No matter what, I still think it makes sense to pick this for 4.12 > rcs, because it also simplifies for us for how to deal with the > mmc+arm64 dependency, since this needs to go together (to avoid > damaging the WiFi chip when power off) > > > > > It would also have been useful if you pointed out the DT contents was > > already acked by Arnd (I had to go look at the contents since you only > > looped him in, and no other ARM-SoC maintainers). > > > > Apologize about that! I will make that clear, if/when next time! > > > > > -Olof > > Kind regards > Uffe -- <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook | <http://twitter.com/#!/linaroorg> Twitter | <http://www.linaro.org/linaro-blog/> Blog ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [GIT PULL] MMC fixes for v.4.12 rc3 - take 2/2 2017-05-29 10:22 ` Daniel Lezcano @ 2017-06-02 0:05 ` Olof Johansson 2017-06-02 10:13 ` Daniel Lezcano 0 siblings, 1 reply; 6+ messages in thread From: Olof Johansson @ 2017-06-02 0:05 UTC (permalink / raw) To: Daniel Lezcano Cc: Ulf Hansson, Linus, linux-mmc, linux-kernel@vger.kernel.org, arm@kernel.org, Arnd Bergmann Hi, On Mon, May 29, 2017 at 12:22:36PM +0200, Daniel Lezcano wrote: > On Sun, May 28, 2017 at 12:26:00PM +0200, Ulf Hansson wrote: > > Hi Olof, > > > > +Daniel > > > > On 26 May 2017 at 18:24, Olof Johansson <olof@lixom.net> wrote: > > > Hi Ulf, > > > > > > > > > On Fri, May 26, 2017 at 6:08 AM, Ulf Hansson <ulf.hansson@linaro.org> wrote: > > >> Hi Linus, > > >> > > >> Here are a couple of mmc and arm64-dts fixes intended for v4.12 rc3. > > >> They are based on v4.12-rc2. > > >> > > >> Details are as usual found in the signed tag. Please pull this in! > > >> > > >> Kind regards > > >> Ulf Hansson > > >> > > >> > > >> The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d: > > >> > > >> Linux 4.12-rc2 (2017-05-21 19:30:23 -0700) > > >> > > >> are available in the git repository at: > > >> > > >> git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git tags/mmc-v4.12-rc2 > > >> > > >> for you to fetch changes up to ea452678734eb782126f999bf5c4fb3e71d3b196: > > >> > > >> arm64: dts: hikey: Fix WiFi support (2017-05-23 14:18:10 +0200) > > >> > > >> ---------------------------------------------------------------- > > >> This pull request contains fixes to make the WiFi work again for the ARM64 > > >> Hikey board. Together with a couple of DTS updates for the Hikey board we have > > >> also extended the mmc pwrseq_simple, to support a new power-off-delay-us DT > > >> property, as that was required to enable a graceful power off sequence for the > > >> WiFi chip. > > >> > > >> ---------------------------------------------------------------- > > >> Daniel Lezcano (2): > > >> mfd: dts: hi655x: Add clock binding for the pmic > > >> arm64: dts: hikey: Add clock for the pmic mfd > > >> > > >> Ulf Hansson (6): > > >> mmc: dt: pwrseq-simple: Invent power-off-delay-us > > >> mmc: pwrseq_simple: Parse DTS for the power-off-delay-us property > > >> arm64: dts: hi6220: Move the fixed_5v_hub regulator to the hikey dts > > >> arm64: dts: hikey: Add the SYS_5V and the VDD_3V3 regulators > > >> arm64: dts: hi6220: Move board data from the dwmmc nodes to hikey dts > > >> arm64: dts: hikey: Fix WiFi support > > > > > > > > > These are a lot of changes to fix a regression. How was it introduced? > > > > It was several releases ago it got broken, exactly which one I can't > > really tell. > > > > I suspect this also is related to an upgrade of the boot loader, as in > > the earlier version of the series there where a pmic clock driver > > included, however it got picked up for 4.12. > > > > Looping in Daniel, just to see if he have some comments on this. > > Depending on the version of the bootloader, the sdio/mmc2 was not correctly set > up and raised a hung task warning. > > This one has been fixed with the commit: > > commit 0fbdf9953b41c28845fe8d05007ff09634ee3000 > Author: Daniel Lezcano <daniel.lezcano@linaro.org> > Date: Thu Mar 16 15:03:24 2017 +0100 > > arm64: dts: hi6220: Reset the mmc hosts > > The MMC hosts could be left in an unconsistent or uninitialized state from > the firmware. Instead of assuming, the firmware did the right things, let's > reset the host controllers. > > This change fixes a bug when the mmc2/sdio is initialized leading to a hung > task: > > [ 242.704294] INFO: task kworker/7:1:675 blocked for more than 120 seconds. > [ 242.711129] Not tainted 4.9.0-rc8-00017-gcf0251f #3 > [ 242.716571] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > [ 242.724435] kworker/7:1 D 0 675 2 0x00000000 > [ 242.729973] Workqueue: events_freezable mmc_rescan > [ 242.734796] Call trace: > [ 242.737269] [<ffff00000808611c>] __switch_to+0xa8/0xb4 > [ 242.742437] [<ffff000008d07c04>] __schedule+0x1c0/0x67c > [ 242.747689] [<ffff000008d08254>] schedule+0x40/0xa0 > [ 242.752594] [<ffff000008d0b284>] schedule_timeout+0x1c4/0x35c > [ 242.758366] [<ffff000008d08e38>] wait_for_common+0xd0/0x15c > [ 242.763964] [<ffff000008d09008>] wait_for_completion+0x28/0x34 > [ 242.769825] [<ffff000008a1a9f4>] mmc_wait_for_req_done+0x40/0x124 > [ 242.775949] [<ffff000008a1ab98>] mmc_wait_for_req+0xc0/0xf8 > [ 242.781549] [<ffff000008a1ac3c>] mmc_wait_for_cmd+0x6c/0x84 > [ 242.787149] [<ffff000008a26610>] mmc_io_rw_direct_host+0x9c/0x114 > [ 242.793270] [<ffff000008a26aa0>] sdio_reset+0x34/0x7c > [ 242.798347] [<ffff000008a1d46c>] mmc_rescan+0x2fc/0x360 > > [ ... ] > > > For the story, this mmc/sdio is for the WiFi and this one was working for some > version of the bootloader which initialized the clock and set the enable line > for the chip. That is bad because the WiFi is working as a side effect from the > boot loader. > > In order to properly make support for the WiFi in the kernel, we need to sort > out this by: > > - Reset the mmc > - Implement the clock at the pmic level > - Add the mfd clock cell > - Add the DT definition Ok, that's all fine but it's not really what we would call a fix. Hardware bringup and enabling of major drivers is usually done through the release cycle and merged in the merge window, not as "fixes" after it's closed. It's not causing problems in this case, but if it happens often it runs the risk of causing a mess due to conflicting contributions from different subsystem maintainers (i.e. in particular the DT contents updates), and in general circumvents the development model we're keeping where things are tested in -next before merge, etc. Anyway, water under the bridge but it's stuff to think about for next time around. -Olof ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [GIT PULL] MMC fixes for v.4.12 rc3 - take 2/2 2017-06-02 0:05 ` Olof Johansson @ 2017-06-02 10:13 ` Daniel Lezcano 0 siblings, 0 replies; 6+ messages in thread From: Daniel Lezcano @ 2017-06-02 10:13 UTC (permalink / raw) To: Olof Johansson Cc: Ulf Hansson, Linus, linux-mmc, linux-kernel@vger.kernel.org, arm@kernel.org, Arnd Bergmann On 02/06/2017 02:05, Olof Johansson wrote: [ ... ] >> For the story, this mmc/sdio is for the WiFi and this one was working for some >> version of the bootloader which initialized the clock and set the enable line >> for the chip. That is bad because the WiFi is working as a side effect from the >> boot loader. >> >> In order to properly make support for the WiFi in the kernel, we need to sort >> out this by: >> >> - Reset the mmc >> - Implement the clock at the pmic level >> - Add the mfd clock cell >> - Add the DT definition > > Ok, that's all fine but it's not really what we would call a fix. Hardware > bringup and enabling of major drivers is usually done through the release > cycle and merged in the merge window, not as "fixes" after it's closed. Yes, I second you on that. That is the reason why I was not really convinced about this series for -rc. > It's not causing problems in this case, but if it happens often it runs > the risk of causing a mess due to conflicting contributions from different > subsystem maintainers (i.e. in particular the DT contents updates), > and in general circumvents the development model we're keeping where > things are tested in -next before merge, etc. > > Anyway, water under the bridge but it's stuff to think about for next time > around. Copy that. Thanks! -- Daniel -- <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook | <http://twitter.com/#!/linaroorg> Twitter | <http://www.linaro.org/linaro-blog/> Blog ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2017-06-02 10:13 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2017-05-26 13:08 [GIT PULL] MMC fixes for v.4.12 rc3 - take 2/2 Ulf Hansson 2017-05-26 16:24 ` Olof Johansson 2017-05-28 10:26 ` Ulf Hansson 2017-05-29 10:22 ` Daniel Lezcano 2017-06-02 0:05 ` Olof Johansson 2017-06-02 10:13 ` Daniel Lezcano
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).