with the fact that the regulator will be initialized after ehci.
Fix this by adding one dependency to the .dts.
Signed-off-by: Alexander Holler hol...@ahsoftware.de
---
arch/arm/boot/dts/kirkwood-dockstar.dts | 4
arch/arm/boot/dts/kirkwood.dtsi | 2 +-
2 files changed, 5 insertions
-by: Alexander Holler hol...@ahsoftware.de
---
drivers/dma/mv_xor.c | 2 +-
drivers/dma/omap-dma.c | 2 +-
drivers/gpio/gpio-mvebu.c | 2 +-
drivers/gpio/gpio-twl4030.c| 2 +-
drivers/i2c/busses/i2c-omap.c | 2 +-
drivers
-by: Alexander Holler hol...@ahsoftware.de
---
arch/arm/mach-omap2/pdata-quirks.c | 8
drivers/pwm/pwm-tipwmss.c | 5 +
2 files changed, 13 insertions(+)
diff --git a/arch/arm/mach-omap2/pdata-quirks.c
b/arch/arm/mach-omap2/pdata-quirks.c
index c33e07e..80becdb 100644
--- a/arch/arm
Use the feature of dependency based initialization order for drivers
if CONFIG_OF_DEPENDENCIES is enabled.
Signed-off-by: Alexander Holler hol...@ahsoftware.de
---
arch/arm/mach-kirkwood/board-dt.c | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/mach-kirkwood/board-dt.c
b
do like this stuff at all.
Do you already want those 3 patches for the standalone dtc?
Regards,
Alexander Holler
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo
higher
languages like C++), therefor I don't even try it and leave further
comments on the ARM assembler to other people. ;)
Regards,
Alexander Holler
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
Mor
. ;)
Regards,
Alexander Holler
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Thanks for proving all my assumptions about kernel maintainers.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
Thanks for proving all my assumptions about kernel maintainers.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
Am 03.04.2014 20:21, schrieb Sebastian Hesselbarth:
On 04/03/2014 07:58 PM, Alexander Holler wrote:
I hope everyone who missed some more information is happy now, otherwise
I (again) wasted time to type a problem description (not to speak about
the already spent time trying to diagnose
Am 03.04.2014 20:21, schrieb Sebastian Hesselbarth:
On 04/03/2014 07:58 PM, Alexander Holler wrote:
[...]
I already knew about problems with netconsole and mv643xx_eth since
4 years, but didn't care a lot because everything else worked flawless,
I even had forgotten that I've enabled netconsole
/version of iproute, dhcp-client, ...) might be involved.
Alexander Holler
BTW: if you want to fix another bug, changing the mtu does reset the
ethernet device. Something special for mv643xx_eth and not very nice. ;)
--
To unsubscribe from this list: send the line "unsubscribe linux-k
o take the almost low hanging fruit. I'm not sure if I
will spend more time on that topic as I already have a working
patch/workaround and the discussion has become a bit tiresome. Sorry.
Regards,
Alexander Holler
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel
have
sent the patch (which I know NOW that it just is a workaround).
Alexander Holler
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
P
Am 03.04.2014 17:14, schrieb David Miller:
From: Alexander Holler
Date: Thu, 03 Apr 2014 17:06:52 +0200
But don't suggest me (or insist on) a time consuming
Bisects are not time consuming, and help developers analyze your
issue tremendously.
Hmm, compiling and booting several dozen
Am 03.04.2014 10:49, schrieb Sebastian Hesselbarth:
On 04/03/2014 09:17 AM, Alexander Holler wrote:
Am 03.04.2014 00:27, schrieb Sebastian Hesselbarth:
On 04/03/2014 12:12 AM, Alexander Holler wrote:
I am curious, how you determined above commit to be the cause of the
regression you
Am 03.04.2014 00:27, schrieb Sebastian Hesselbarth:
On 04/03/2014 12:12 AM, Alexander Holler wrote:
I am curious, how you determined above commit to be the cause of the
regression you are seeing. Can you bisect, if you didn't already?
There was no bisecting necessary. I've just looked
Am 03.04.2014 10:49, schrieb Sebastian Hesselbarth:
On 04/03/2014 09:17 AM, Alexander Holler wrote:
Am 03.04.2014 00:27, schrieb Sebastian Hesselbarth:
On 04/03/2014 12:12 AM, Alexander Holler wrote:
I am curious, how you determined above commit to be the cause of the
regression you
Am 03.04.2014 17:14, schrieb David Miller:
From: Alexander Holler hol...@ahsoftware.de
Date: Thu, 03 Apr 2014 17:06:52 +0200
But don't suggest me (or insist on) a time consuming
Bisects are not time consuming, and help developers analyze your
issue tremendously.
Hmm, compiling and booting
have
sent the patch (which I know NOW that it just is a workaround).
Alexander Holler
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
hanging fruit. I'm not sure if I
will spend more time on that topic as I already have a working
patch/workaround and the discussion has become a bit tiresome. Sorry.
Regards,
Alexander Holler
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
/version of iproute, dhcp-client, ...) might be involved.
Alexander Holler
BTW: if you want to fix another bug, changing the mtu does reset the
ethernet device. Something special for mv643xx_eth and not very nice. ;)
--
To unsubscribe from this list: send the line unsubscribe linux-kernel
Am 03.04.2014 20:21, schrieb Sebastian Hesselbarth:
On 04/03/2014 07:58 PM, Alexander Holler wrote:
[...]
I already knew about problems with netconsole and mv643xx_eth since
4 years, but didn't care a lot because everything else worked flawless,
I even had forgotten that I've enabled netconsole
Am 03.04.2014 20:21, schrieb Sebastian Hesselbarth:
On 04/03/2014 07:58 PM, Alexander Holler wrote:
I hope everyone who missed some more information is happy now, otherwise
I (again) wasted time to type a problem description (not to speak about
the already spent time trying to diagnose
Am 03.04.2014 00:27, schrieb Sebastian Hesselbarth:
On 04/03/2014 12:12 AM, Alexander Holler wrote:
I am curious, how you determined above commit to be the cause of the
regression you are seeing. Can you bisect, if you didn't already?
There was no bisecting necessary. I've just looked
Am 02.04.2014 22:25, schrieb Sebastian Hesselbarth:
> On 04/02/2014 09:01 PM, Florian Fainelli wrote:
>> 2014-04-02 2:09 GMT-07:00 Alexander Holler :
>>> Am 02.04.2014 02:57, schrieb Florian Fainelli:
>>>> 2014-04-01 16:55 GMT-07:00 A
ht make sense to wait for some other users to complain, I think it
won't need long as this SOC is used in Sheevaplugs and Dockstars, some
ARMv5 devices which were quiet popular. Or if nobody else complains,
maybe someone might test my change. Ut could be possible that the
failing sequence is through
Am 02.04.2014 11:09, schrieb Alexander Holler:
Am 02.04.2014 02:57, schrieb Florian Fainelli:
2014-04-01 16:55 GMT-07:00 Alexander Holler :
Commit 7cd1463664c2a15721ff4ccfb61d4d970815cb3d (introduced with 3.14)
changed the initialization of the mv643xx_eth driver to use
phy_init_hw()
to reset
Am 02.04.2014 02:57, schrieb Florian Fainelli:
2014-04-01 16:55 GMT-07:00 Alexander Holler :
Commit 7cd1463664c2a15721ff4ccfb61d4d970815cb3d (introduced with 3.14)
changed the initialization of the mv643xx_eth driver to use phy_init_hw()
to reset the PHY. Unfortunately the initialization
Am 02.04.2014 02:57, schrieb Florian Fainelli:
2014-04-01 16:55 GMT-07:00 Alexander Holler hol...@ahsoftware.de:
Commit 7cd1463664c2a15721ff4ccfb61d4d970815cb3d (introduced with 3.14)
changed the initialization of the mv643xx_eth driver to use phy_init_hw()
to reset the PHY. Unfortunately
Am 02.04.2014 11:09, schrieb Alexander Holler:
Am 02.04.2014 02:57, schrieb Florian Fainelli:
2014-04-01 16:55 GMT-07:00 Alexander Holler hol...@ahsoftware.de:
Commit 7cd1463664c2a15721ff4ccfb61d4d970815cb3d (introduced with 3.14)
changed the initialization of the mv643xx_eth driver to use
,
maybe someone might test my change. Ut could be possible that the
failing sequence is through the/my use of netconsole, which is, I
assume, not very common.
Regards,
Alexander Holler
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord
Am 02.04.2014 22:25, schrieb Sebastian Hesselbarth:
On 04/02/2014 09:01 PM, Florian Fainelli wrote:
2014-04-02 2:09 GMT-07:00 Alexander Holler hol...@ahsoftware.de:
Am 02.04.2014 02:57, schrieb Florian Fainelli:
2014-04-01 16:55 GMT-07:00 Alexander Holler hol...@ahsoftware.de:
Commit
to finish.
The effect was that the ethernet on my Kirkwood 88F6281 based device didn't
come up anymore (no carrier).
Fix this by waiting for a reset to finish before proceeding further.
Signed-off-by: Alexander Holler
Cc: Michal Simek
Cc: Florian Fainelli
Cc:
---
drivers/net/phy/marvell.c | 8
. ;)
Regards,
Alexander Holler
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Am 01.04.2014 20:36, schrieb Kees Cook:
On Tue, Apr 1, 2014 at 11:03 AM, Laura Abbott wrote:
On 4/1/2014 3:04 AM, Alexander Holler wrote:
CONFIG_DEBUG_SET_MODULE_RONX sounds like a nice security feature, but
things might fail late (and unexpected) if module code is set to read-only
while
Am 01.04.2014 14:23, schrieb Michal Marek:
On 2014-04-01 13:23, Alexander Holler wrote:
But as I already said, trying to use arbitrary filenames in a Makefile
doesn't really work. There are still other problems, e.g. filenames with
a / (directory separator), *, or some of the special make
Am 31.03.2014 22:31, schrieb Michal Marek:
Dne 22.3.2014 19:22, Alexander Holler napsal(a):
Am 22.03.2014 13:29, schrieb Alexander Holler:
The initramfs generation is broken for file and directory names which
contain
colons, spaces and other unusual characters. Print an error and don't
try
CONFIG_DEBUG_SET_MODULE_RONX sounds like a nice security feature, but
things might fail late (and unexpected) if module code is set to read-only
while CONFIG_JUMP_LABEL is enabled (e.g. modprobe bridge).
Avoid this.
Signed-off-by: Alexander Holler
---
arch/arm/Kconfig.debug | 2 +-
1 file
CONFIG_DEBUG_SET_MODULE_RONX sounds like a nice security feature, but
things might fail late (and unexpected) if module code is set to read-only
while CONFIG_JUMP_LABEL is enabled (e.g. modprobe bridge).
Avoid this.
Signed-off-by: Alexander Holler hol...@ahsoftware.de
---
arch/arm/Kconfig.debug
Am 31.03.2014 22:31, schrieb Michal Marek:
Dne 22.3.2014 19:22, Alexander Holler napsal(a):
Am 22.03.2014 13:29, schrieb Alexander Holler:
The initramfs generation is broken for file and directory names which
contain
colons, spaces and other unusual characters. Print an error and don't
try
Am 01.04.2014 14:23, schrieb Michal Marek:
On 2014-04-01 13:23, Alexander Holler wrote:
But as I already said, trying to use arbitrary filenames in a Makefile
doesn't really work. There are still other problems, e.g. filenames with
a / (directory separator), *, or some of the special make
Am 01.04.2014 20:36, schrieb Kees Cook:
On Tue, Apr 1, 2014 at 11:03 AM, Laura Abbott lau...@codeaurora.org wrote:
On 4/1/2014 3:04 AM, Alexander Holler wrote:
CONFIG_DEBUG_SET_MODULE_RONX sounds like a nice security feature, but
things might fail late (and unexpected) if module code is set
. ;)
Regards,
Alexander Holler
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
to finish.
The effect was that the ethernet on my Kirkwood 88F6281 based device didn't
come up anymore (no carrier).
Fix this by waiting for a reset to finish before proceeding further.
Signed-off-by: Alexander Holler hol...@ahsoftware.de
Cc: Michal Simek michal.si...@xilinx.com
Cc: Florian Fainelli
Am 26.03.2014 23:37, schrieb Alexander Holler:
Am 26.03.2014 22:55, schrieb Alexander Holler:
Am 26.03.2014 22:38, schrieb Levente Kurusa:
This is walkable but probably not worth the effort. Besides, why would
anyone want to put spaces, colons and arbitrary characters to filenames
Am 26.03.2014 23:37, schrieb Alexander Holler:
Am 26.03.2014 22:55, schrieb Alexander Holler:
Am 26.03.2014 22:38, schrieb Levente Kurusa:
This is walkable but probably not worth the effort. Besides, why would
anyone want to put spaces, colons and arbitrary characters to filenames
Am 26.03.2014 22:55, schrieb Alexander Holler:
Am 26.03.2014 22:38, schrieb Levente Kurusa:
What I think might be reasonable is:
- get rid of the dependency list in form of a include into the
Makefile and
just generate the cpio-archive every time make is called. Common
initramfs
sizes
Am 26.03.2014 22:38, schrieb Levente Kurusa:
Hi,
2014-03-26 22:16 GMT+01:00 Alexander Holler :
Am 22.03.2014 00:07, schrieb Alexander Holler:
Am 21.03.2014 23:55, schrieb Andrew Morton:
On Fri, 21 Mar 2014 23:49:57 +0100 Alexander Holler
wrote:
Am 21.03.2014 22:03, schrieb Andrew Morton
Am 22.03.2014 00:07, schrieb Alexander Holler:
Am 21.03.2014 23:55, schrieb Andrew Morton:
On Fri, 21 Mar 2014 23:49:57 +0100 Alexander Holler
wrote:
Am 21.03.2014 22:03, schrieb Andrew Morton:
On Thu, 20 Mar 2014 23:00:45 +0100 Alexander Holler
wrote:
The initramfs generation
Am 22.03.2014 00:07, schrieb Alexander Holler:
Am 21.03.2014 23:55, schrieb Andrew Morton:
On Fri, 21 Mar 2014 23:49:57 +0100 Alexander Holler hol...@ahsoftware.de
wrote:
Am 21.03.2014 22:03, schrieb Andrew Morton:
On Thu, 20 Mar 2014 23:00:45 +0100 Alexander Holler hol...@ahsoftware.de
Am 26.03.2014 22:38, schrieb Levente Kurusa:
Hi,
2014-03-26 22:16 GMT+01:00 Alexander Holler hol...@ahsoftware.de:
Am 22.03.2014 00:07, schrieb Alexander Holler:
Am 21.03.2014 23:55, schrieb Andrew Morton:
On Fri, 21 Mar 2014 23:49:57 +0100 Alexander Holler
hol...@ahsoftware.de wrote:
Am
Am 26.03.2014 22:55, schrieb Alexander Holler:
Am 26.03.2014 22:38, schrieb Levente Kurusa:
What I think might be reasonable is:
- get rid of the dependency list in form of a include into the
Makefile and
just generate the cpio-archive every time make is called. Common
initramfs
sizes
Am 26.03.2014 00:36, schrieb Alexander Holler:
Am 25.03.2014 19:38, schrieb Alexander Holler:
reboot too. Another solution would be to unregister the reboot_notifier
in the reboot_nofifier itself. I've just seen one watchdog driver
(drivers/rtc/rtc-m41t80.c) which does that. But I still think
Am 25.03.2014 19:38, schrieb Alexander Holler:
reboot too. Another solution would be to unregister the reboot_notifier
in the reboot_nofifier itself. I've just seen one watchdog driver
(drivers/rtc/rtc-m41t80.c) which does that. But I still think such
That, btw. is broken. ;)
Right after
be to unregister the reboot_notifier
in the reboot_nofifier itself. I've just seen one watchdog driver
(drivers/rtc/rtc-m41t80.c) which does that. But I still think such
shouldn't be necessary (and I haven't had a look at other
reboot_notifier users).
Regards,
Alexander Holler
--
To unsubscribe from
solution would be to unregister the reboot_notifier
in the reboot_nofifier itself. I've just seen one watchdog driver
(drivers/rtc/rtc-m41t80.c) which does that. But I still think such
shouldn't be necessary (and I haven't had a look at other
reboot_notifier users).
Regards,
Alexander Holler
Am 25.03.2014 19:38, schrieb Alexander Holler:
reboot too. Another solution would be to unregister the reboot_notifier
in the reboot_nofifier itself. I've just seen one watchdog driver
(drivers/rtc/rtc-m41t80.c) which does that. But I still think such
That, btw. is broken. ;)
Right after
Am 26.03.2014 00:36, schrieb Alexander Holler:
Am 25.03.2014 19:38, schrieb Alexander Holler:
reboot too. Another solution would be to unregister the reboot_notifier
in the reboot_nofifier itself. I've just seen one watchdog driver
(drivers/rtc/rtc-m41t80.c) which does that. But I still think
Am 22.03.2014 13:29, schrieb Alexander Holler:
The initramfs generation is broken for file and directory names which contain
colons, spaces and other unusual characters. Print an error and don't try to
continue.
(...)
+ # Files and directories with spaces and colons are unsupported
blem with spaces:
mkdir -p /tmp/bugroot/a\ b
make -j4 bzImage # no error
zcat usr/initramfs_data.cpio.gz | cpio --extract --list # oops, no content
Signed-off-by: Alexander Holler
Cc:
---
Changes in v2, v3: check for \n, \r and \t too, updated error msg.
scripts/gen_initramfs_list.sh | 13
dependency list too.
Avoid that by not including this dependency list for make goals (dist)clean.
Signed-off-by: Alexander Holler
Cc:
---
usr/Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/usr/Makefile b/usr/Makefile
index e767f01..5d5b6aa 100644
--- a/usr/Makefile
+++ b/usr
Am 22.03.2014 00:07, schrieb Alexander Holler:
Am 21.03.2014 23:55, schrieb Andrew Morton:
Should we check for \t and \n as well?
Hmm, maybe. But usually there aren't filenames wich do contain those
characters, and if you want to break (or exploit) the kernel build
process, there are easier
Am 22.03.2014 00:07, schrieb Alexander Holler:
Am 21.03.2014 23:55, schrieb Andrew Morton:
Should we check for \t and \n as well?
Hmm, maybe. But usually there aren't filenames wich do contain those
characters, and if you want to break (or exploit) the kernel build
process, there are easier
dependency list too.
Avoid that by not including this dependency list for make goals (dist)clean.
Signed-off-by: Alexander Holler hol...@ahsoftware.de
Cc: sta...@vger.kernel.org
---
usr/Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/usr/Makefile b/usr/Makefile
index e767f01..5d5b6aa
bzImage # no error
zcat usr/initramfs_data.cpio.gz | cpio --extract --list # oops, no content
Signed-off-by: Alexander Holler hol...@ahsoftware.de
Cc: sta...@vger.kernel.org
---
Changes in v2, v3: check for \n, \r and \t too, updated error msg.
scripts/gen_initramfs_list.sh | 13
Am 22.03.2014 13:29, schrieb Alexander Holler:
The initramfs generation is broken for file and directory names which contain
colons, spaces and other unusual characters. Print an error and don't try to
continue.
(...)
+ # Files and directories with spaces and colons are unsupported
Am 21.03.2014 23:55, schrieb Andrew Morton:
> On Fri, 21 Mar 2014 23:49:57 +0100 Alexander Holler
> wrote:
>
>> Am 21.03.2014 22:03, schrieb Andrew Morton:
>>> On Thu, 20 Mar 2014 23:00:45 +0100 Alexander Holler
>>> wrote:
>>>
>>>> The
Am 21.03.2014 22:03, schrieb Andrew Morton:
> On Thu, 20 Mar 2014 23:00:45 +0100 Alexander Holler
> wrote:
>
>> The initramfs generation is broken for file and directory names which contain
>> colons or spaces. Print an error and don't try to continue.
> It would be bet
Am 21.03.2014 09:28, schrieb Linus Walleij:
On Tue, Mar 18, 2014 at 10:45 AM, Alexander Holler wrote:
But I don't need any rush here, I'm just unable to understand why the -rc
phase isn't used for bug fixing as I believe that's what this phase is for.
Right now it is mostly a practical
Am 21.03.2014 09:28, schrieb Linus Walleij:
On Tue, Mar 18, 2014 at 10:45 AM, Alexander Holler hol...@ahsoftware.de wrote:
But I don't need any rush here, I'm just unable to understand why the -rc
phase isn't used for bug fixing as I believe that's what this phase is for.
Right now
Am 21.03.2014 22:03, schrieb Andrew Morton:
On Thu, 20 Mar 2014 23:00:45 +0100 Alexander Holler hol...@ahsoftware.de
wrote:
The initramfs generation is broken for file and directory names which contain
colons or spaces. Print an error and don't try to continue.
It would be better to fix
Am 21.03.2014 23:55, schrieb Andrew Morton:
On Fri, 21 Mar 2014 23:49:57 +0100 Alexander Holler hol...@ahsoftware.de
wrote:
Am 21.03.2014 22:03, schrieb Andrew Morton:
On Thu, 20 Mar 2014 23:00:45 +0100 Alexander Holler hol...@ahsoftware.de
wrote:
The initramfs generation is broken
Am 20.03.2014 23:00, schrieb Alexander Holler:
The initramfs generation is broken for file and directory names which contain
colons or spaces. Print an error and don't try to continue.
I will not send a v3, but I think this is a candidate for the stable
kernels too, as the problem might drive
bugroot/a\ b
make -j4 bzImage # no error
zcat usr/initramfs_data.cpio.gz | cpio --extract --list # oops, no content
Signed-off-by: Alexander Holler
---
Silly and trivial changes in v2: Fixed a typo and added 'colons and spaces'
scripts/gen_initramfs_list.sh | 12
1 file changed
bugroot/a\ b
make -j4 bzImage # no error
zcat usr/initramfs_data.cpio.gz | cpio --extract --list # oops, no content
Signed-off-by: Alexander Holler
---
scripts/gen_initramfs_list.sh | 11 +++
1 file changed, 11 insertions(+)
diff --git a/scripts/gen_initramfs_list.sh b/scripts/gen_initram
/initramfs_data.cpio.gz | cpio --extract --list # oops, no content
Signed-off-by: Alexander Holler hol...@ahsoftware.de
---
scripts/gen_initramfs_list.sh | 11 +++
1 file changed, 11 insertions(+)
diff --git a/scripts/gen_initramfs_list.sh b/scripts/gen_initramfs_list.sh
index 17fa901
/initramfs_data.cpio.gz | cpio --extract --list # oops, no content
Signed-off-by: Alexander Holler hol...@ahsoftware.de
---
Silly and trivial changes in v2: Fixed a typo and added 'colons and spaces'
scripts/gen_initramfs_list.sh | 12
1 file changed, 12 insertions(+)
diff --git
Am 20.03.2014 23:00, schrieb Alexander Holler:
The initramfs generation is broken for file and directory names which contain
colons or spaces. Print an error and don't try to continue.
I will not send a v3, but I think this is a candidate for the stable
kernels too, as the problem might drive
and
thus users.
Regards,
Alexander Holler
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
and
thus users.
Regards,
Alexander Holler
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
boards at least LEDs?
I can confirm the patch does not break my gpiolib based test module
(test with and without DT), but then it did not have an issue even before.
Thanks, maybe someone could add a
Cc:
to get the fix back into 3.14 if it has go through -next.
Regards,
Alexander Holler
,
Alexander Holler
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
. And 2001 is a masterpiece of slowness.
Regards,
Alexander Holler
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FA
. And 2001 is a masterpiece of slowness.
Regards,
Alexander Holler
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
Am 14.03.2014 14:54, schrieb Linus Walleij:
On Fri, Mar 14, 2014 at 1:38 PM, Alexander Holler wrote:
In that case it is hardly a fix that we need to rush out to the entire
world.
And I thought the reason for -rc is actually to fix bugs. But I never
understood the magical ways and timings
Am 14.03.2014 12:02, schrieb Linus Walleij:
On Fri, Mar 14, 2014 at 11:08 AM, Alexander Holler wrote:
Am 11.03.2014 11:15, schrieb Linus Walleij:
On Wed, Mar 5, 2014 at 12:21 PM, Alexander Holler wrote:
The driver missed an of_xlate function to translate gpio numbers
as found in the DT
Am 11.03.2014 11:15, schrieb Linus Walleij:
> On Wed, Mar 5, 2014 at 12:21 PM, Alexander Holler
> wrote:
>
>> The driver missed an of_xlate function to translate gpio numbers
>> as found in the DT to the correct chip and number.
>>
>> While there I've set
Am 11.03.2014 11:15, schrieb Linus Walleij:
On Wed, Mar 5, 2014 at 12:21 PM, Alexander Holler hol...@ahsoftware.de
wrote:
The driver missed an of_xlate function to translate gpio numbers
as found in the DT to the correct chip and number.
While there I've set #gpio_cells to a fixed value
Am 14.03.2014 12:02, schrieb Linus Walleij:
On Fri, Mar 14, 2014 at 11:08 AM, Alexander Holler hol...@ahsoftware.de wrote:
Am 11.03.2014 11:15, schrieb Linus Walleij:
On Wed, Mar 5, 2014 at 12:21 PM, Alexander Holler hol...@ahsoftware.de wrote:
The driver missed an of_xlate function
Am 14.03.2014 14:54, schrieb Linus Walleij:
On Fri, Mar 14, 2014 at 1:38 PM, Alexander Holler hol...@ahsoftware.de wrote:
In that case it is hardly a fix that we need to rush out to the entire
world.
And I thought the reason for -rc is actually to fix bugs. But I never
understood the magical
for gpio-leds in a DT. So I didn't
reinvent the wheel but just copied and tested stuff.
Thanks to Grygorii Strashko for the hint to the existing code in gpio-pxa.
Signed-off-by: Alexander Holler
Signed-off-by: Grygorii Strashko
---
drivers/gpio/gpio-davinci.c | 24
1 file
for gpio-leds in a DT. So I didn't
reinvent the wheel but just copied and tested stuff.
Thanks to Grygorii Strashko for the hint to the existing code in gpio-pxa.
Signed-off-by: Alexander Holler hol...@ahsoftware.de
Signed-off-by: Grygorii Strashko grygorii.stras...@ti.com
---
drivers/gpio/gpio
for gpio-leds in a DT. So I didn't
reinvent the wheel but just copied and tested stuff.
Thanks to Grygorii Strashko for the hint of the existing code in gpio-pxa.
Signed-off-by: Alexander Holler
---
drivers/gpio/gpio-davinci.c | 27 +++
1 file changed, 27 insertions(+)
diff
for gpio-leds in a DT. So I didn't
reinvent the wheel but just copied and tested stuff.
Thanks to Grygorii Strashko for the hint of the existing code in gpio-pxa.
Signed-off-by: Alexander Holler hol...@ahsoftware.de
---
drivers/gpio/gpio-davinci.c | 27 +++
1 file changed, 27
since 3.8 likely earlier than I did (which was
around 3.10 if I remember correctly).
Regards,
Alexander Holler
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
Holler
So feel free to add that if someone thinks it makes sense based on my
short test description above and it isn't already too late.
Thanks again,
Alexander Holler
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
Holler hol...@ahsoftware.de
So feel free to add that if someone thinks it makes sense based on my
short test description above and it isn't already too late.
Thanks again,
Alexander Holler
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord
since 3.8 likely earlier than I did (which was
around 3.10 if I remember correctly).
Regards,
Alexander Holler
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo
;work unwinding" ;)
Regards,
Alexander Holler
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
701 - 800 of 1445 matches
Mail list logo
