Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] linux5.1: networking fixes
Date: Thu, 06 Jun 2019 18:14:53 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12209@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 323 bytes --]

There is a new pull request by thomas-t-w against master on the void-packages repository

https://github.com/thomas-t-w/void-packages linux-network
https://github.com/void-linux/void-packages/pull/12209

linux5.1: networking fixes


A patch file from https://github.com/void-linux/void-packages/pull/12209.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-linux-network-12209.patch --]
[-- Type: application/text/x-diff, Size: 2209 bytes --]

From ae23b38960f18ea87d973a37ca80fd8683097f02 Mon Sep 17 00:00:00 2001
From: Thomas <thomasw@fastmail.cn>
Date: Thu, 6 Jun 2019 12:05:59 -0400
Subject: [PATCH] linux5.1: networking fixes

---
 srcpkgs/linux5.1/files/i386-dotconfig   | 10 +++++-----
 srcpkgs/linux5.1/files/x86_64-dotconfig | 10 +++++-----
 2 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/srcpkgs/linux5.1/files/i386-dotconfig b/srcpkgs/linux5.1/files/i386-dotconfig
index 7d1b8670867..505370f13ce 100644
--- a/srcpkgs/linux5.1/files/i386-dotconfig
+++ b/srcpkgs/linux5.1/files/i386-dotconfig
@@ -2678,9 +2678,9 @@ CONFIG_NET_VENDOR_HUAWEI=y
 CONFIG_HINIC=m
 CONFIG_NET_VENDOR_I825XX=y
 CONFIG_NET_VENDOR_INTEL=y
-CONFIG_E100=y
-CONFIG_E1000=y
-CONFIG_E1000E=y
+CONFIG_E100=m
+CONFIG_E1000=m
+CONFIG_E1000E=m
 CONFIG_E1000E_HWTS=y
 CONFIG_IGB=m
 CONFIG_IGB_HWMON=y
@@ -2991,12 +2991,12 @@ CONFIG_ATH9K_COMMON=m
 CONFIG_ATH9K_BTCOEX_SUPPORT=y
 CONFIG_ATH9K=m
 CONFIG_ATH9K_PCI=y
-# CONFIG_ATH9K_AHB is not set
+CONFIG_ATH9K_AHB=y
 # CONFIG_ATH9K_DEBUGFS is not set
 # CONFIG_ATH9K_DYNACK is not set
 CONFIG_ATH9K_WOW=y
 CONFIG_ATH9K_RFKILL=y
-# CONFIG_ATH9K_CHANNEL_CONTEXT is not set
+CONFIG_ATH9K_CHANNEL_CONTEXT=y
 CONFIG_ATH9K_PCOEM=y
 CONFIG_ATH9K_HTC=m
 # CONFIG_ATH9K_HTC_DEBUGFS is not set
diff --git a/srcpkgs/linux5.1/files/x86_64-dotconfig b/srcpkgs/linux5.1/files/x86_64-dotconfig
index 547cef1a001..75bafffa2d6 100644
--- a/srcpkgs/linux5.1/files/x86_64-dotconfig
+++ b/srcpkgs/linux5.1/files/x86_64-dotconfig
@@ -2738,9 +2738,9 @@ CONFIG_NET_VENDOR_HUAWEI=y
 CONFIG_HINIC=m
 CONFIG_NET_VENDOR_I825XX=y
 CONFIG_NET_VENDOR_INTEL=y
-CONFIG_E100=y
-CONFIG_E1000=y
-CONFIG_E1000E=y
+CONFIG_E100=m
+CONFIG_E1000=m
+CONFIG_E1000E=m
 CONFIG_E1000E_HWTS=y
 CONFIG_IGB=m
 CONFIG_IGB_HWMON=y
@@ -3056,12 +3056,12 @@ CONFIG_ATH9K_COMMON=m
 CONFIG_ATH9K_BTCOEX_SUPPORT=y
 CONFIG_ATH9K=m
 CONFIG_ATH9K_PCI=y
-# CONFIG_ATH9K_AHB is not set
+CONFIG_ATH9K_AHB=y
 # CONFIG_ATH9K_DEBUGFS is not set
 # CONFIG_ATH9K_DYNACK is not set
 CONFIG_ATH9K_WOW=y
 CONFIG_ATH9K_RFKILL=y
-# CONFIG_ATH9K_CHANNEL_CONTEXT is not set
+CONFIG_ATH9K_CHANNEL_CONTEXT=y
 CONFIG_ATH9K_PCOEM=y
 CONFIG_ATH9K_HTC=m
 # CONFIG_ATH9K_HTC_DEBUGFS is not set

             reply	other threads:[~2019-06-06 16:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-06 16:14 voidlinux-github [this message]
2019-06-06 16:37 ` [PR PATCH] [Merged]: " voidlinux-github

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12209@inbox.vuxu.org \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).