From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 32787fb0dff053a4a31f9785ddb3f40e1d6a6063
Date: Sun, 07 Dec 2014 10:56:15 +0100 [thread overview]
Message-ID: <20141207095615.5530821214@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1790 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, master has been updated
via 32787fb0dff053a4a31f9785ddb3f40e1d6a6063 (commit)
from 0c5dcca2eeb2aea50fd52ce411c4255c4cc2b942 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 32787fb0dff053a4a31f9785ddb3f40e1d6a6063
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Dec 7 10:55:24 2014 +0100
kernel: add patches for rt5572 wlan chipset.
-----------------------------------------------------------------------
Summary of changes:
lfs/linux | 2 ++
1 file changed, 2 insertions(+)
Difference in files:
diff --git a/lfs/linux b/lfs/linux
index 2644711..dac6275 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -140,6 +140,8 @@ endif
cd $(DIR_APP) && patch -Np1 < $(DIR_SRC)/src/patches/linux-3.14.22-iwlwifi-noibss_only_on_radar_chan.patch
cd $(DIR_APP) && patch -Np1 < $(DIR_SRC)/src/patches/linux-3.10.37-rt2800usb_add_dlink_dwa137_usbid.patch
cd $(DIR_APP) && patch -Np1 < $(DIR_SRC)/src/patches/linux-3.10.55-rt2800usb-change_queue_warn_to_debug.patch
+ cd $(DIR_APP) && patch -Np1 < $(DIR_SRC)/src/patches/linux-3.14.25_rt2x00_fix_bss_bcn_num.patch
+ cd $(DIR_APP) && patch -Np1 < $(DIR_SRC)/src/patches/linux-3.14.25-rt5592_no_special_txop_init.patch
cd $(DIR_APP) && patch -Np1 < $(DIR_SRC)/src/patches/linux-3.10.39-add_libertas_uap.patch
# mISDN Patches
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-12-07 9:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141207095615.5530821214@argus.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox