From: Joe Perches <joe@perches.com>
To: gregkh@linuxfoundation.org
Cc: LKML <linux-kernel@vger.kernel.org>, netdev <netdev@vger.kernel.org>
Subject: Re: patch "staging: MAINTAINERS: remove obsolete IPX staging directory" added to staging-testing
Date: Tue, 16 Oct 2018 04:43:30 -0700 [thread overview]
Message-ID: <249981aa5af26de07565946fbe806e3c01f26c07.camel@perches.com> (raw)
In-Reply-To: <15396867728666@kroah.com>
On Tue, 2018-10-16 at 12:46 +0200, gregkh@linuxfoundation.org wrote:
> This is a note to let you know that I've just added the patch titled
>
> staging: MAINTAINERS: remove obsolete IPX staging directoryts
[]
> From dd71c89b2c1ae049d2018107e9d7a41261db3f7b Mon Sep 17 00:00:00 2001
> From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Date: Tue, 16 Oct 2018 12:45:13 +0200
> Subject: staging: MAINTAINERS: remove obsolete IPX staging directory
>
> The IPX code was removed from staging back in November 2017, but the
> MAINTAINERS entry stuck around. Remove the invalid directory from the
> file as it does not actually point to anything anymore.
As the uapi ipx file still exists but the functionality
has been removed, perhaps some compiler message like
#pragma message "IPX functionality removed as of linux kernel v4.18"
should be added to the uapi file.
> diff --git a/MAINTAINERS b/MAINTAINERS
> []
> @@ -7672,7 +7672,6 @@ IPX NETWORK LAYER
> L: netdev@vger.kernel.org
> S: Obsolete
> F: include/uapi/linux/ipx.h
> -F: drivers/staging/ipx/
>
> IRQ DOMAINS (IRQ NUMBER MAPPING LIBRARY)
> M: Marc Zyngier <marc.zyngier@arm.com>
next parent reply other threads:[~2018-10-16 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15396867728666@kroah.com>
2018-10-16 11:43 ` Joe Perches [this message]
2018-10-16 11:51 ` Greg KH
2018-10-16 17:11 ` Joe Perches
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=249981aa5af26de07565946fbe806e3c01f26c07.camel@perches.com \
--to=joe@perches.com \
--cc=gregkh@linuxfoundation.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
all inboxes | Powered by JetHome®