This replaces the current patches used to make the kernel headers
compatible with musl with the version which was accepted upstream and
the other patches working on top of that.
This was compile tested with iproute2 build on all supported kernel
versions with musl and one one with glibc.
Signed-of
On 01/02/2018 07:26 PM, Sandeep Sheriker wrote:
> Hi Hauke,
>
> I get below build error
>
> make -C
> /home/sandeep/microchip/arm/lede/build_dir/target-arm_cortex-a5+neon-vfpv4_musl_eabi/u-boot-sama5d2_xplained_mmc/u-boot-2016.05
> sama5d2_xplained_mmc_config
> make[4]: Entering directory
> '/ho
Use the default build definitions instead of some custom one. The custom
one added -mfloat-abi=soft which is used in the kernel build and the
normal -mfloat-abi=hard was added in addition which caused a build
problem.
Fixes: 01cc6bd495f31 ("at91: sama5: activate fpu")
Signed-off-by: Hauke Mehrtens
Hi,
> I'm unable to reproduce the reported netifd crash by using a proto
> shell handler having no proto_init_config function.
> Looking into the code the proto_handler config_params parameter is
> always assigned the proto shell handler config pointer in the function
> proto_shell_add_handler; af
On Wed, Jan 3, 2018 at 10:35 AM, Olof Sivertsson wrote:
> When ubus invokes proto_dump_handlers, and a struct proto_handler has
> been added with a NULL config_params, a segmentation fault occurs.
>
> Avoid this segmentation fault by checking for a NULL config_params
> before further access.
Hi,
On 12/15/2017 03:10 PM, Roman Yeryomin wrote:
> There is a race between `cp -a /tmp/root/* /rom/overlay` from
> libfstools/overlay.c and a process creating new file(s) before
> pivot(/rom, /mnt) occured.
> That is a process can create a file and it will not be copied.
>
> To workaround this, do ad
On 01/03/2018 04:21 AM, Y.b. Lu wrote:
> Hi Hauke,
>
> The layerscape maintainer info should be no problem. You just sent wrong
> email address to me. (cyangbo...@nxp.com)
> MAINTAINER:=Yangbo Lu
Will you send a patch to update the Maintainer?
> I will cherry-pick this patch to our internal LE
Refresh patches
Signed-off-by: Kevin Darbyshire-Bryant
---
include/kernel-version.mk | 4 +-
.../patches-4.4/910-unaligned_access_hacks.patch | 2 +-
.../generic/pending-4.4/208-disable-modorder.patch | 4 +-
.../pending-4.4/653-disable_netlink_trim.patch | 2 +
Refresh patches.
Run-tested: ar71xx Archer C7 v2
Signed-off-by: Kevin Darbyshire-Bryant
Tested-by: Stijn Segers
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Hi Kevin,
FYI - I am getting these messages when applying:
$ git am
../patches/main/0001-kernel-update-17.01-kernel-4.4-to-4.4.109.patch
Applying: kernel: bump 4.4 to 4.4.109 for 17.01
.git/rebase-apply/patch:86: space before tab in indent.
xhci->quirks |= XHCI_TRUST_TX_LENGTH;
.git/rebase-a
Refresh patches.
Run-tested: ar71xx Archer C7 v2
Signed-off-by: Kevin Darbyshire-Bryant
---
include/kernel-version.mk | 4 +-
...d-firmware-loader-for-uPD720201-and-uPD72.patch | 6 +-
.../802-usb-xhci-force-msi-renesas-xhci.patch | 4 +-
.../patches-4.4/910-una
Upstream commit "PCI: Do not allocate more buses than available in
parent" limits the amount of busses being allocated upon scanning the
PCIe bus. [1]
This commit was introduced in kernel 4.9.71
This breaks PCIe scanning on the Gateworks Ventana, causing no devices
to be found.
Temp fix this by
Hi all,
If someone can help me, I have error building sudo, something about PAM
I tried including pam lib and enabling pam in busybox but with no avail
it's latest openwrt/lede git
Thank you!
--
checking for pam_start in -lpam... yes
checking security/pam_appl.h usability... no
checking securi
From: Rafał Miłecki
Aside from just cleaning up mountd's tmp dir it's also important for
autofs support. With such an empty directory autofs_process_request
believed device is mounted and it kept replying AUTOFS_IOC_READY to the
kernel. It was causing a log storm like:
mountd[1015]: Got a autofs
From: Rafał Miłecki
Calling an extra rmdir and unlink isn't a big issue but triggering
hotplug.d scripts for devices that weren't mounted could be misleading
for listeners.
Signed-off-by: Rafał Miłecki
---
mount.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a
From: Rafał Miłecki
If mounting fails for whatever reason (like unsupported file system or
something) hotplug.d scripts shouldn't be called.
Signed-off-by: Rafał Miłecki
---
mount.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/mount.c b/mount.c
index caf9d9d..803acc1
On Tue, Jan 2, 2018 at 11:01 PM, Rosen Penev wrote:
> On Mon, Dec 25, 2017 at 3:23 PM, Florian Fainelli
> wrote:
>> Le 12/25/17 à 15:05, Rosen Penev a écrit :
>>> Reduction of 48 bytes in compiled size. No functional difference.
>>>
>>> -pedantic was removed as %m is a GNU extension.
>>
>> My 2
When ubus invokes proto_dump_handlers, and a struct proto_handler has
been added with a NULL config_params, a segmentation fault occurs.
Avoid this segmentation fault by checking for a NULL config_params
before further access.
Signed-off-by: Olof Sivertsson
---
proto.c | 2 +-
1 file changed, 1
18 matches
Mail list logo
