From: Xie He <xie.he.0141@gmail.com>
To: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Lee Jones <lee.jones@linaro.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: Xie He <xie.he.0141@gmail.com>
Subject: [PATCH net-next] net/socket.c: Remove an unused header file <linux/if_frad.h>
Date: Thu, 10 Sep 2020 23:07:20 -0700 [thread overview]
Message-ID: <20200911060720.81033-1-xie.he.0141@gmail.com> (raw)
This header file is not actually used in this file. Let's remove it.
Information about this header file:
This header file comes from the "Frame Relay" module at
drivers/net/wan/dlci.c
The "Frame Relay" module is used by only one hardware driver, at:
drivers/net/wan/sdla.c
Note that the "Frame Relay" module is different from and unrelated to the
"HDLC Frame Relay" module at:
drivers/net/wan/hdlc_fr.c
I think maybe we can deprecate the "Frame Relay" module because we already
have the (newer) "HDLC Frame Relay" module.
Signed-off-by: Xie He <xie.he.0141@gmail.com>
---
net/socket.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/net/socket.c b/net/socket.c
index 82262e1922f9..161dd2775e13 100644
--- a/net/socket.c
+++ b/net/socket.c
@@ -64,7 +64,6 @@
#include <linux/seq_file.h>
#include <linux/mutex.h>
#include <linux/if_bridge.h>
-#include <linux/if_frad.h>
#include <linux/if_vlan.h>
#include <linux/ptp_classify.h>
#include <linux/init.h>
--
2.25.1
next reply other threads:[~2020-09-11 6:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 6:07 Xie He [this message]
2020-09-11 14:57 ` [PATCH net-next] net/socket.c: Remove an unused header file <linux/if_frad.h> Jakub Kicinski
2020-09-11 21:41 ` David Miller
2020-09-11 23:30 ` Xie He
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=20200911060720.81033-1-xie.he.0141@gmail.com \
--to=xie.he.0141@gmail.com \
--cc=davem@davemloft.net \
--cc=gustavoars@kernel.org \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).