[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- > On Aug 25, 2020, at 6:24 AM,

[no subject]

at 7:28 PM, Adrian Schmutzler wrote: > > Hi again, > >> -Original Message- >> From: Raylynn Knight [mailto:raykni...@me.com] >> Sent: Montag, 24. August 2020 10:00 >> To: Adrian Schmutzler >> Cc: OpenWrt Development List ; >> ro...@advem.lv

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Hello, I've tried OpenWrt

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Result from using sysupgrade:

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- I’m interested in adding support

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Signed-off-by: Sandeep Sheriker M

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- changing dtb file path since the

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- bump version to linux4sam-2020.04

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Signed-off-by: Sandeep Sheriker M

[no subject]

uest. > Reply-To: Organization: > > I sent an email to cont...@openwrt.org, subject line Trademark Use > Request, inquiring about crowd funding an OpenWrt router.  I never > received a reply.  The email gave the background, links to forum > discussion and a poll and outlined the basic struc

[no subject]

problem, the original message has been wrapped >> automatically by the mailing list software. > >> Date: Tue, 4 Aug 2020 20:35:26 -0300 >> From: SAn >> To: Daniel Golle , s@gmx.de >> Cc: openwrt-devel@lists.openwrt.org >> Subject: Re: your mail >&

[no subject]

On 8/2/20 8:19 PM, Daniel Golle wrote: > On Sun, Aug 02, 2020 at 07:49:40PM -0300, SAn via openwrt-devel wrote: >> Subject: ath79 subtarget with cmdline from bootloader >> >> Hi! >> >> The LibreRouter uses a dual-boot scheme that relies on the bootloader >>

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Hi! The LibreRouter uses a

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Вокально-Инструментальные

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- ЛУЧШИЕ ПСИХОЛОГИЧЕСКИЕ ТРЕНИНГИ И

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- > Until now it has not been

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- АУДИОКНИГИ "МОДЕЛЬ ДЛЯ СБОРКИ"

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- СОВЕТСКИЕ МУЛЬТФИЛЬМЫ Большая

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- РАДИОСПЕКТАКЛИ, РАССКАЗЫ,

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Hi Luca, On Sun, Jul 5, 2020 at

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Hi Luca, On Sun, Jul 5, 2020 at

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Hi Luca, On Sun, Jul 5, 2020 at

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Fix at least one rare wave-2

[no subject]

wed up in my mailbox with an empty subject. The patch is also not being picked up by Patchwork. I will probably have to mail the patch again to get it processed, but I'm starting to feel annoyed by causing all this noise on the list with my resubmissions. Patch messages 2020-06-23: https://lists.inf

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- okli images always have the

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- [resubmission after openwrt-devel

[no subject]

--- Begin Message --- The hardware appears to be identical to R6260/R6350/R6850. The factory image has been confirmed to work with nmrpflash. Signed-off-by: Jan Hoffmann --- .../ramips/dts/mt7621_netgear_wac124.dts | 25 +++ target/linux/ramips/image/mt7621.mk |

[no subject]

--- Begin Message --- Commit 76f9aa6f4bfd12fba34fc44aef890c48d4fb1024 should backport support for mvneta XDP, but I can't load it. # ip link set dev eth0 xdp obj /tmp/bpf.o sec xdp1 RTNETLINK answers: Not supported strace output: set_tls(0xb6f5f5d8) = 0

[no subject]

ot; header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software. - have a blank subject. I'm not so sure i like a whole bunch of mails with blank subjects, is there anything that can be done to fix it? --- E

[no subject]

--- Begin Message --- Hi Deng, On 25/06/2020 20:32, DENG Qingfang wrote: Commit 76f9aa6f4bfd12fba34fc44aef890c48d4fb1024 should backport support for mvneta XDP, but I can't load it. # ip link set dev eth0 xdp obj /tmp/bpf.o sec xdp1 RTNETLINK answers: Not supported strace output:

[no subject]

--- Begin Message --- The original code required the use of relative addresses into the lua stack. It should accept either. Signed-off-by: Karl Palsson --- lua/uloop.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/lua/uloop.c b/lua/uloop.c index fcbe274..394970d 100644

[no subject]

--- Begin Message --- Some minor improvements to argument handling and docs. Patches 2 and 3 are optional, they have zero functional change, but IMO make the code easier to follow for future workers. --- End Message --- ___ openwrt-devel mailing

[no subject]

--- Begin Message --- Zstd is supported by the crypto API since Linux 4.18. Enable this feature and reveal the package in the configuration section, so the user can select it. This allows zstd to be used as a compression algorithm in zram, for example. Signed-off-by: Rui Salvaterra ---

[no subject]

--- Begin Message --- Hi, the subtarget mpc85xx/generic has been renamed to mpc85xx/p1010 in commit: https://github.com/openwrt/openwrt/commit/564f87ef5bea16d5d1d8a9a80e8de77429159f26 Unfortunately, nobody has though of updating the buildbots, so images are frozen at that date and the buildbot

[no subject]

--- Begin Message --- Hi, I just had a look at the buildbots and found that there seems to be a build error for mt7629, no images build since May 3! http://buildbot.openwrt.org/master/images/builders/mediatek%2Fmt7629 A local build with buildbot settings on my Debian 10 VM went through fine,

[no subject]

--- Begin Message --- Zstd is supported by the crypto API since Linux 4.18. Enable this feature and reveal the package in the configuration section, so the user can select it. This allows zstd to be used as a compression algorithm in zram, for example. Signed-off-by: Rui Salvaterra ---

[no subject]

--- Begin Message --- The two main changes are that Prefix Informations are only sent for prefixes the router is responsible for and that Route Informations are sent for all prefixes. This allows to send router advertisements on the wan interface to tell hosts there about the routes available via

[no subject]

--- Begin Message --- Hi Rui, no offence, but I do not have direct commit right to openwrt's repo. I've had done some work on zram-script before, that's why I was interested in this case. You could try to create a PR to GiHub's openwrt repo than someone from the core team could pick it up

[no subject]

--- Begin Message --- Instead of having to adjust the index repeatedly as the stack is manipulated, use absolute addressing for the function arguments, so they stay the same throughout the call. Zero functional change, just subjectively easier to follow variables. Signed-off-by: Karl Palsson

[no subject]

--- Begin Message --- Actually check for flags being valid, instead of simply ignoring the call if flags was zero. Use standard lua checks for the function argument, so you can get a normal "argument #2 was invalid, expected function, got xxx" instead of the vague, "invalid arg list"

[no subject]

--- Begin Message --- Ran into some issues with my fd event being garbage collected. As I never wanted to call :delete, I had seen no reason to keep the returned object, as my callback and upvalues were still valid. Signed-off-by: Karl Palsson --- examples/uloop-example.lua | 8 +--- 1

[no subject]

--- Begin Message --- Hi, Emil, After pressing send, I realised my choice of words made my previous email sound harsh, it wasn't my intention, I'm sorry about that. :) On Thu, 25 Jun 2020 at 18:13, Emil Muratov wrote: > > Hi Rui, > no offence, but I do not have direct commit right to openwrt's

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Hi Rui, no, of cource I mean not

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Hmm... that looks weird at

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- On 23.06.2020 14:29, Rui

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- To enable dynamic kernel/rootfs

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- okli images always have the

[no subject]

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Hi John, On Tue, Jun 23, 2020 at

Re: [OpenWrt-Devel] Subject: [PATCH 1/1] blobmsg_json: allow to add full json files

point me in the right direction I can add the corresponding tests. Adrián -Original Message- From: Petr Štetiar Sent: miércoles, 3 de junio de 2020 05:03 a. m. To: Adrian Panella Cc: openwrt-devel@lists.openwrt.org Subject: Re: [OpenWrt-Devel] Subject: [PATCH 1/1] blobmsg_json: allow

Re: [OpenWrt-Devel] Subject: [PATCH 1/1] blobmsg_json: allow to add full json files

Hi, next time please do: $ git format-patch -s1 --subject-prefix "PATCH libubox" ... as described in https://openwrt.org/submitting-patches Adrian Panella [2020-02-22 20:11:28]: > Current function "blobmsg_add_json_from_file" only adds json file if it is > an ob

[OpenWrt-Devel] (no subject)

Hello, This is my second attempt to fix the snapshot images for D-Link DIR 860L B1. This device accepts uncompressed uImages as initramfs only. >From the flash it expects LZMA compressed image and ignores the uImage header. To create a bootable image, the LZMA packed kernel prepared with

[OpenWrt-Devel] Subject: [PATCH 1/1] blobmsg_json: allow to add full json files

Current function "blobmsg_add_json_from_file" only adds json file if it is an object, and it only returns the properties, not a full object attribute. This version allows to read any valid json file and returns the complete corresponding attribute. Signed-off-by: Adrian Panella ---

Re: [OpenWrt-Devel] (no subject)

Hi, Have you checked https://openwrt.org/trademark ? Cheers! El 11/12/19 a les 20:43, sagar jain ha escrit: > > Can i sell OpenWRT based router ? > >   > > Sent from Mail for > Windows 10 > >   > > >

[OpenWrt-Devel] (no subject)

Can i sell OpenWRT based router ? Sent from Mail for Windows 10 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] (no subject)

زبان چینی رابه انگلیسی تغییردهید ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] (no subject)

Sent from Mail for Windows 10 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] (no subject)

Code de admin ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Subject: [PATCH 2/2] ath79: GL.iNet AR300M family: Correct DTS LED definitions

00:00 2001 From: Jeff Kletsky Date: Sun, 20 Jan 2019 14:48:09 -0800 Subject: [PATCH 2/2] ath79: GL.iNet AR300M family: Correct DTS LED definitions Change the "status" LED to proper GPIO 12 and "red" naming. Remove GPIO 2 from definition as a USB LED. GPIO 2 is used to c

[OpenWrt-Devel] (no subject)

adding kmod-mt76x0e enables the 5GHz radio on the TP-Link wr902ac-v3 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] (no subject)

ubus default timeout is 30 seconds so having rpcd file timeout longer would be nice as some commands first need to gather data then output. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org

[OpenWrt-Devel] (no subject)

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Since upgrading to 2.1.8 is a

[OpenWrt-Devel] (no subject)

Hi Everyone, Tomorrow we will have the prplwrt working group meeting at 9am PT/18:00 CEST. Dial in information is below. Agenda: * OpenWrt Survey — let Shelly know if you want to review it one last time before it is broadcast * Summit — reminder that Call for Proposals is open until the end

Re: [OpenWrt-Devel] (no subject)

On 14 June 2016 at 06:04, Jerome <jeromepou...@gmail.com> wrote: > To: openwrt-devel@lists.openwrt.org > From: =?UTF-8?q?J=C3=A9r=C3=B4me=20Poulin?= <jeromepou...@gmail.com> > Date: Mon, 13 Jun 2016 17:47:50 -0400 > Subject: [PATCH] micropython-lib: fix make install seld

[OpenWrt-Devel] (no subject)

To: openwrt-devel@lists.openwrt.org From: =?UTF-8?q?J=C3=A9r=C3=B4me=20Poulin?= <jeromepou...@gmail.com> Date: Mon, 13 Jun 2016 17:47:50 -0400 Subject: [PATCH] micropython-lib: fix make install seldom fail - Since make install path was hardcoded inside the build dir, it can sometime

[OpenWrt-Devel] (no subject)

Hi, I can see a couple of months ago a patch was submitted to allow the wr802n to work as expected, but at the time it looks like it was rejected because it was not submitted properly: https://lists.openwrt.org/pipermail/openwrt-devel/2016-February/039591.html Do you know if any progress was

Re: [OpenWrt-Devel] (no subject)

@lists.openwrt.org Subject: RE: [OpenWrt-Devel] (no subject) Hi Mike, Sorry, not technical enough to help out with that... Hope someone else can help you out. Cheers Stijn ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https

Re: [OpenWrt-Devel] (no subject)

Hi Mike, Sorry, not technical enough to help out with that... Hope someone else can help you out. Cheers Stijn ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] (no subject)

25Q32FVS1G (not clear - can't make out about half in the photo) R/ Mike -Original Message- From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On Behalf Of Stijn Segers Sent: Friday, March 25, 2016 3:36 AM To: openwrt-devel@lists.openwrt.org Subject: [OpenWrt-Devel

[OpenWrt-Devel] (no subject)

Subject: [PATCH] ar71xx: Add preliminary TL-WR841N/ND v11 support This patch adds preliminary support for the TP-Link TL-WR841N/ND to trunk. It is similar to the already supported v10 [1]. I have added support based on that topic but since I do not have the device myself I am looking for testers

[OpenWrt-Devel] (no subject)

Subject: [PATCH] CC: ar71xx: Bitmain Antminer S1 & S3 cleanup Sets the LEDs to boardname:color:led-name Sets the LAN to eth0 Corrects the profile names in the Makefile and changes tabs to spaces in the Makefile 'define Device/' like the other devices. Other corrections such as the Machine

[OpenWrt-Devel] Subject: [PATCH] [target] Addition of NixCore X1 Board

from: Andrew Gaylo This submission is for a the NixCore X1 board. This board uses the RT5350 Ralink processor already supported by a number of board in the OpenWRT repository. The DTS and profile MK provided is based on existing boards included in the repo (VoCore).

[OpenWrt-Devel] (no subject)

Subject: [PATCH] ramips: Fix Ticket #20153 swap radio calibration data pointers on the RE6500 This patch fixes weak radio signal reported by nikola.georgiev Signed-off-by: L. D. Pinney ldpin...@gmail.com --- Patch applies to CC as well. target/linux/ramips/dts/RE6500.dts | 4 ++-- 1 file

[OpenWrt-Devel] (no subject)

Hey everybody, I'm trying to build a Barrier Breaker image with OpenVswitch 2.3.1. However, it fails with {standard input}:1116: Error: unknown pseudo-op: `.tprelword' error. I found [a Stack Overflow thread](http://stackoverflow.com/questions/8872517) that suggests this is due to a too old

[OpenWrt-Devel] (no subject)

https://lists.openwrt.org/cgi-bin/mailman/confirm/openwrt-devel/20d2b3e1caa737fae52aa05e7568d63432844198 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] (no subject)

Hi, The wiki page for http://wiki.openwrt.org/doc/howto/hardware.button refers to https://dev.openwrt.org/changeset/37336 procd: make old button hotplug rules work until all packages are migrated Which imply that procd took over hotplug buttons, and that there's a proper way that packages

Re: [OpenWrt-Devel] (no subject)

On 19/01/2015 16:54, Karl Palsson wrote: Hi, The wiki page for http://wiki.openwrt.org/doc/howto/hardware.button refers to https://dev.openwrt.org/changeset/37336 procd: make old button hotplug rules work until all packages are migrated Which imply that procd took over hotplug

Re: [OpenWrt-Devel] Subject: [PATCH] [package] Check port state on new call to avoid previous call ending

Hello Roberto, thank you for your contribution. You seem to have swapped the original and modified source file while diffing it, but this is a not a big deal. I will test your change during this week and merge it if it works. Next time please create pull request against the github telephony

[OpenWrt-Devel] (no subject)

The following changes since commit 576d8531a744377b1c9e322d8d1533474064b880: [ar71xx]: fix the r6100's wan led name (2014-11-26 11:38:59 +) are available in the git repository at: https://gitorious.org/openwrt-oxnas/openwrt-oxnas.git for you to fetch changes up to

[OpenWrt-Devel] (no subject)

Patch to add the buildprofile for the GL-Init-6408A-v1 and the GL-Inet-6416A-v1 Both devices are identical, only difference is one comes with 8MB flash and the other with 16MB flash Official website: http://www.gl-inet.com/w/?page_id=241lang=en Comprehensive list of specs:

[OpenWrt-Devel] Subject: [PATCH] Busybox: Fix pam_start link errors when PAM support is enabled

From: Stephen G. Parry sgpa...@mainscreen.com Patch to BusyBox Makefile to fix linker errors when PAM support is enabled by CONFIG_BUSYBOX_CONFIG_PAM=y. Typical errors include: login.c:(.text.login_main+0x122): undefined reference to `pam_start' Signed-off-by: Stephen Parry

Re: [OpenWrt-Devel] Subject: [PATCH] Busybox: Fix pam_start link errors when PAM support is enabled

I have sent as a git patch. I will follow up with an svn one. Please let me know which is more preferable. If possible please apply to BB as well as trunk. Thanks. On 15/08/14 17:25, Stephen Parry wrote: From: Stephen G. Parry sgpa...@mainscreen.com Patch to BusyBox Makefile to fix linker

Re: [OpenWrt-Devel] Subject: [PATCH] Busybox: Fix pam_start link errors when PAM support is enabled

On Fri, Aug 15, 2014 at 6:32 PM, Stephen Parry sgpa...@mainscreen.com wrote: I have sent as a git patch. I will follow up with an svn one. Please let me know which is more preferable. Please don't, sending the patch once is enough. Jonas ___

[OpenWrt-Devel] Subject: [PATCH 1/1] [package] Rework gnokii package to offer sendsms subpackage and the smsd service.

From: Andreas Thienemann andr...@bawue.net Offer better SMS integration for the gnokii package: gnokii-sendsms is a ncurses/dialog based frontend to interactively send a SMS message through a supported modem. gnoki-smsd is a SMS spooling service based on gnokii. Messages dropped into a

[OpenWrt-Devel] (no subject)

From 4454a29846b8c580dc380b108cfa8e48a13ff67a Mon Sep 17 00:00:00 2001 From: W. Michael Petullo m...@flyn.org Date: Fri, 7 Mar 2014 21:58:27 -0500 Subject: [PATCH 3/6] Add base plugins for GStreamer 1.0 To: openwrt-devel@lists.openwrt.org Signed-off-by: W. Michael Petullo m...@flyn.org

[OpenWrt-Devel] (no subject)

From f45f723f81bfa889556526f0a5c0ce7ae5ff10b3 Mon Sep 17 00:00:00 2001 From: W. Michael Petullo m...@flyn.org Date: Fri, 7 Mar 2014 22:34:17 -0500 Subject: [PATCH 4/6] Good plugins for GStreamer 1.0. To: openwrt-devel@lists.openwrt.org Signed-off-by: W. Michael Petullo m...@flyn.org

[OpenWrt-Devel] (no subject)

From 4648b73df7eff02ff7f8633b06bb4a48bb172d9b Mon Sep 17 00:00:00 2001 From: W. Michael Petullo m...@flyn.org Date: Fri, 7 Mar 2014 22:34:56 -0500 Subject: [PATCH 6/6] Ugly plugins for GStreamer 1.0. To: openwrt-devel@lists.openwrt.org Signed-off-by: W. Michael Petullo m...@flyn.org

[OpenWrt-Devel] (no subject)

From 42ce62f764ec046620fbdc2120f1891a22dd966b Mon Sep 17 00:00:00 2001 From: W. Michael Petullo m...@flyn.org Date: Fri, 7 Mar 2014 21:57:00 -0500 Subject: [PATCH 2/6] Many applications are starting to require GStreamer 1.0, which is API-incompatible with GStreamer 0.10. The name gstreamer1

[OpenWrt-Devel] (no subject)

From ff2e304c49fc5efc549558f3c958ed439c1d942f Mon Sep 17 00:00:00 2001 From: W. Michael Petullo m...@flyn.org Date: Fri, 7 Mar 2014 22:34:39 -0500 Subject: [PATCH 5/6] Bad plugins for GStreamer 1.0. To: openwrt-devel@lists.openwrt.org Signed-off-by: W. Michael Petullo m...@flyn.org

[OpenWrt-Devel] (no subject)

From 0e3d0fc4fef035b210250d927640e677f1f4bf88 Mon Sep 17 00:00:00 2001 From: W. Michael Petullo m...@flyn.org Date: Fri, 7 Mar 2014 21:56:14 -0500 Subject: [PATCH 1/6] Fix build of glib2 on Fedora 20 To: openwrt-devel@lists.openwrt.org Signed-off-by: W. Michael Petullo m...@flyn.org --- libs

[OpenWrt-Devel] [PATCH 0/2] *** SUBJECT HERE ***

*** BLURB HERE *** Oliver Ertl (2): pyload: update to current version 0.4.9 pyload: add LIBCURL_COOKIES dependency net/pyload/Makefile | 8 1 file changed, 4 insertions(+), 4 deletions(-) -- 1.8.3.2 ___ openwrt-devel mailing list

Re: [OpenWrt-Devel] [PATCH 0/2] *** SUBJECT HERE ***

On Fri, Jan 31, 2014 at 10:31 AM, Oliver Ertl oli...@ertls-netzwerk.de wrote: *** BLURB HERE *** I guess you forgot to fill in something here. Jonas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org

Re: [OpenWrt-Devel] [PATCH 0/2] *** SUBJECT HERE ***

Ok, you can delete the patches then. No need for the patch then :-( Am 31. Januar 2014 12:38:43 schrieb Jonas Gorski j...@openwrt.org: On Fri, Jan 31, 2014 at 10:31 AM, Oliver Ertl oli...@ertls-netzwerk.de wrote: *** BLURB HERE *** I guess you forgot to fill in something here. Jonas

Re: [OpenWrt-Devel] [PATCH 0/2] *** SUBJECT HERE ***

On 01/31/2014 01:49 PM, Oliver Ertl wrote: Ok, you can delete the patches then. No need for the patch then :-( Hey Oliver , it's just the patch guideline , Jonas trying to help you submit a full decent patch, no need to be upset ;-) Am 31. Januar 2014 12:38:43 schrieb Jonas Gorski

Re: [OpenWrt-Devel] [PATCH 0/2] *** SUBJECT HERE ***

On Fri, Jan 31, 2014 at 1:34 PM, Daniel Petre daniel.pe...@gmail.com wrote: On 01/31/2014 01:49 PM, Oliver Ertl wrote: Ok, you can delete the patches then. No need for the patch then :-( Hey Oliver , it's just the patch guideline , Jonas trying to help you submit a full decent patch, no

[OpenWrt-Devel] (no subject)

Hi, I'm trying to get the second UART working on a WR841N v8. The AR9341 SoC does have a AR9330 and a 8250 style UART, which is normally the console. I'm facing some problems to get it working. Does anybody tried to get similar working ? AFAIK the only difference between the AR934x high speed

[OpenWrt-Devel] Subject: [PATCH] [toolchain] musl: add 0.9.10 support

...@...ts.openwall.com +Cc: Abdoulaye Walsimou Gaye a...@...toolkit.org +Subject: [PATCH 3/4] Import BSD functions defined in netinet/ether.h from NetBSD + +Signed-off-by: Abdoulaye Walsimou Gaye a...@...toolkit.org +--- + include/netinet/ether.h | 14 + src/network/ethers.c| 180

Re: [OpenWrt-Devel] Subject: [PATCH] [toolchain] musl: add 0.9.10 support

I noticed that the patch was not properly submitted. I did compose the patch on plain text format but the parser somehow mixed it up. The three lines after 'diffstat' output should be at the end of the patch. --- BEGIN --- +-- +1.7.9.5 + --- END --- Do I have to submit it again? If so, how to do

[OpenWrt-Devel] (no subject)

Index: target/linux/ar71xx/generic/profiles/allnet.mk === --- target/linux/ar71xx/generic/profiles/allnet.mk (revision 0) +++ target/linux/ar71xx/generic/profiles/allnet.mk (revision 0) @@ -0,0 +1,41 @@ +# +# Copyright (C)

[OpenWrt-Devel] (no subject)

Index: sound/mpc/patches/01-uclibc.patch === --- sound/mpc/patches/01-uclibc.patch (Revision 0) +++ sound/mpc/patches/01-uclibc.patch (Revision 0) @@ -0,0 +1,15 @@ +Index: mpc-0.15/src/main.c

<    1   2