Re: [OpenWrt-Devel] Backporting from dev branch to stable

Basically speaking ... one would take the working patch set from trunk and apply it to CC ... fix all the errors, changes, etc. Then once you have a working patch set for CC ... submit it. A couple of recent examples : https://patchwork.ozlabs.org/patch/505724/ and https://patchwork.ozlabs.org/pa

Re: [OpenWrt-Devel] [PATCH v2] base-files: init/sysfixtime - exclude dnsmasq.time

Hi, hope this comment is not too late :) On 23 September 2015 at 17:12, Steven Barth wrote: > Using --dnssec-no-timecheck is impractical since it reacts to SIGHUP which > is already overloaded and might be triggered by e.g. config changes. > Agree. I did not check the source code, but it's bad

Re: [OpenWrt-Devel] Backporting from dev branch to stable

Guys with more experience will certainly be better suited to answer, but from what I've observed, something like new device support wouldn't be appropriate to backport into a released branch. Usually only critical security patches are backported. There has been discussion of 15.05 working as a LT

[OpenWrt-Devel] [PATCH] base-files: add URL option for OEM manufacturer info

This URL can be embedded e.g. within UPnP announcements where a link to the manufacturer's homepage is desired. Signed-off-by: Michael Heimpold --- include/version.mk |5 + package/base-files/files/etc/device_info |1 + package/base-files/image-config.in |

[OpenWrt-Devel] Backporting from dev branch to stable

Hi all, how are the patches from main development branch backported to Chaos Calmer branch from dev branch? Do I have to re-post this patch-set http://git.openwrt.org/?p=openwrt.git;a=commit;h=c84682a79e36bb57f4f78d51aa589f7bfe3fb5e8 against this branch: http://git.openwrt.org/?p=15.05/openwrt.git

[OpenWrt-Devel] [PATCH v3 1/3] ramips: Add DTS files for HiWiFi HC5x61 models

HiWiFi HC5661/5761/5861 models are manufactured by http://www.hiwifi.com. These models have similar hardware specs(MT7620A + 128M DDR2 + 16M flash). This patch adds support for them. The original author is Justin Liu (rss...@gmail.com). I ported the patch to trunk and submitted it here with his

[OpenWrt-Devel] [PATCH V3 3/3] ramips: Add build files for HiWiFi HC5x61 models

HiWiFi HC5661/5761/5861 models are manufactured by http://www.hiwifi.com . These models have similar hardware specs(MT7620A + 128M DDR2 + 16M flash). This patch adds support for them. The original author is Justin Liu (rss...@gmail.com). I ported the patch to trunk and s

[OpenWrt-Devel] [PATCH V3 2/3] ramips: Add base-files for HiWiFi HC5x61 models

HiWiFi HC5661/5761/5861 models are manufactured by http://www.hiwifi.com. These models have similar hardware specs(MT7620A + 128M DDR2 + 16M flash). This patch adds support for them. The original author is Justin Liu (rss...@gmail.com). I ported the patch to trunk and submitted it here with his

[OpenWrt-Devel] help

Am Tue, 29 Sep 2015 15:32:15 +0200 schrieb openwrt-devel-requ...@lists.openwrt.org: > Send openwrt-devel mailing list submissions to > openwrt-devel@lists.openwrt.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.openwrt.org/cgi-bin/mailman/listinfo/ope

[OpenWrt-Devel] unsubscribe

Am Tue, 29 Sep 2015 12:00:02 +0200 schrieb openwrt-devel-requ...@lists.openwrt.org: > Send openwrt-devel mailing list submissions to > openwrt-devel@lists.openwrt.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.openwrt.org/cgi-bin/mailman/listinfo/ope

[OpenWrt-Devel] [PATCH][odhcpd] Limit size of IPv4 DHCP reply

Limit size of IPv4 DHCP reply. In other words, remove zero padding after end option (0xff). Signed-off-by: Dmitry Ivanov --- src/dhcpv4.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/dhcpv4.c b/src/dhcpv4.c index a657e13..c8014ea 100644 --- a/src/dhcpv4.c +++ b/src/dhc

Re: [OpenWrt-Devel] periodic task checking for usb flash media?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Karl Palsson wrote: > Hi, > > I've got a custom board with an onboard USB flash media > interface. It works well, I can mount and access micro SD cards > nicely, and all that basic stuff. > > However, card detection doesn't work. The USB flash inter

[OpenWrt-Devel] [PATCH] base-files: create /var/tmp on boot

FHS mandates presence of /var/tmp on compliant systems. The lack of /var/tmp was discovered when using MIT Kerberos libraries which default to that location for storing credentials cache. Signed-off-by: Paul Fertser --- package/base-files/files/etc/init.d/boot | 1 + 1 file changed, 1 insertion

[OpenWrt-Devel] periodic task checking for usb flash media?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I've got a custom board with an onboard USB flash media interface. It works well, I can mount and access micro SD cards nicely, and all that basic stuff. However, card detection doesn't work. The USB flash interface is Mass Storage Bulk Only, and

[OpenWrt-Devel] [PATCH] [SIGNED-OFF] Correct WeIO board name

Trivial parch to correct WeIO board name in the system. Signed-off-by: Drasko DRASKOVIC --- target/linux/ar71xx/base-files/lib/ar71xx.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/ar71xx/base-files/lib/ar71xx.sh b/target/linux/ar71xx/base-files/lib/ar71xx.s

Re: [OpenWrt-Devel] [PATCH netifd] netifd-proto.sh: add table argument to proto_add_ipv4_route()

Alexander, I don't have a problem with that particular patch. However since the other patch was redundant and the only user of this one it seemed redundant to me as well. If you have another usecase for this then please let us know. Cheers, Steven On 29.09.2015 11:37, Alexander Couzens wrote:

Re: [OpenWrt-Devel] [PATCH netifd] netifd-proto.sh: add table argument to proto_add_ipv4_route()

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Steven, you rejected this patch as well. Why would you not allow to define a specific table for ipv4, but for ipv6? > cy...@openwrt.org > NAK. Use "option ip4table" and "option ip6table" which works with > all protocols already. -BEGIN PGP