Re: [OpenWrt-Devel] Booting D-Link DNS-313, kernel requirements for OpenWRT?

On Wed, Jan 17, 2018 at 6:11 PM, Hans Ulli Kroll wrote: > Hi Linus >> I managed to boot a v4.16-ish kernel and OpenWRT rootfs >> on the D-Link DNS-313 >> (reference https://dflund.se/~triad/krad/dlink-dns-313/) > > interesting device, especially for the VBUS

Re: [OpenWrt-Devel] [PATCH 0/5] x86: add support for microcode update

On 17/01/18 20:41, Zoltan HERPAI wrote: Hi, This series will add support for microcode update on x86 targets, in light of the recent security issues. While other distributions use an early initramfs approach to update the microcode as early as possible, in OpenWrt the earliest place where we

Re: [OpenWrt-Devel] [LEDE-DEV] [PATCH 0/5] x86: add support for microcode update

On 01/18/2018 01:51 PM, Nick Lowe wrote: > Does an update to the Kernel, 4.9.77 and 4.14.14 need to be made to > properly address this? There are fixes to mitigate Spectre. We even need a patch for GCC which will be in GCC 8 and 7.3. For master we should backport it to GCC 5.5, but what do we

Re: [OpenWrt-Devel] [LEDE-DEV] [PATCH 2/5] firmware: add microcode package for AMD64

On 01/17/2018 08:41 PM, Zoltan HERPAI wrote: > Signed-off-by: Zoltan HERPAI > --- > package/firmware/linux-firmware/x86.mk | 9 + > 1 file changed, 9 insertions(+) > create mode 100644 package/firmware/linux-firmware/x86.mk > > diff --git

Re: [OpenWrt-Devel] [LEDE-DEV] [PATCH 0/5] x86: add support for microcode update

On Thu, 18 Jan 2018, Hauke Mehrtens wrote: On 01/18/2018 01:51 PM, Nick Lowe wrote: Does an update to the Kernel, 4.9.77 and 4.14.14 need to be made to properly address this? There are fixes to mitigate Spectre. We even need a patch for GCC which will be in GCC 8 and 7.3. For master we

[OpenWrt-Devel] Enable DCO check on Github OpenWrt organisation

Hi All, Could someone enable this https://github.com/integration/dco on the whole OpenWrt github org? (or at least on the packages repo) Thanks Etienne ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org

Re: [OpenWrt-Devel] patchwork

Hi All, 2018-01-18 1:30 GMT-08:00 Piotr Dymacz : > Hi, > > On 18.01.2018 09:44, Jo-Philipp Wich wrote: >> >> Hi John, Alex, >> >> I have no problem with closing / autorejecting open tickets in patchwork >> as long as they somehow remain available for future reference. > > > ACK.

Re: [OpenWrt-Devel] [LEDE-DEV] [PATCH 2/5] firmware: add microcode package for AMD64

On Thu, 18 Jan 2018, Hauke Mehrtens wrote: On 01/17/2018 08:41 PM, Zoltan HERPAI wrote: Signed-off-by: Zoltan HERPAI --- package/firmware/linux-firmware/x86.mk | 9 + 1 file changed, 9 insertions(+) create mode 100644 package/firmware/linux-firmware/x86.mk diff

[OpenWrt-Devel] patchwork

Hi, I would like to close all ~1000 un-handled patches from the last 3 years and only keep stuff from the last 6 months. any problem with that ?     John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org

Re: [OpenWrt-Devel] patchwork

On Thu, Jan 18, 2018 at 10:31 AM, John Crispin wrote: > Hi, > > I would like to close all ~1000 un-handled patches from the last 3 years and > only keep stuff from the last 6 months. any problem with that ? > To add here. Would it be possible/desire-able to add an auto-timeout

Re: [OpenWrt-Devel] patchwork

Hi John, Alex, I have no problem with closing / autorejecting open tickets in patchwork as long as they somehow remain available for future reference. > To add here. Would it be possible/desire-able to add an auto-timeout > to patchwork & github PRs, issues to close after X time ? Maybe make >

Re: [OpenWrt-Devel] patchwork

Hi, On 18.01.2018 09:44, Jo-Philipp Wich wrote: Hi John, Alex, I have no problem with closing / autorejecting open tickets in patchwork as long as they somehow remain available for future reference. ACK. Would it be possible to send the author short message why the patch was auto

Re: [OpenWrt-Devel] patchwork

Hi, On Thu, 18 Jan 2018, John Crispin wrote: Hi, I would like to close all ~1000 un-handled patches from the last 3 years and only keep stuff from the last 6 months. any problem with that ? No objections, if something was missed in the last 3 years (and is not in trunk already), then it'd

[OpenWrt-Devel] merging mailing lists

Hi, Please provide me with a dump of all mail addresses / names currently subscribed s.T. we can setup the new ML and send out auto generated invite mails.     John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org