linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	devel@driverdev.osuosl.org
Subject: Re: [PATCH] MAINTAINERS: mark wusbcore and UWB as obsolete
Date: Thu, 08 Aug 2019 04:15:44 -0700	[thread overview]
Message-ID: <92ed89b0346a54fb06d3e08585a8d0b4175842f0.camel@perches.com> (raw)
In-Reply-To: <20190808094158.GA22635@kroah.com>

On Thu, 2019-08-08 at 11:41 +0200, Greg Kroah-Hartman wrote:
> On Thu, Aug 08, 2019 at 11:25:09AM +0200, Greg Kroah-Hartman wrote:
> > Joe rightly points out that we should be using the "Obsolete" status for
> > these two subsystems.
> 
> Even with that change, I don't see get_maintainers.pl tell me I
> shouldn't be sending a patch in for this area:

Nor should you.  It's checkpatch that should warn.

> 
> 
> $ cat x.patch
> diff --git a/drivers/staging/uwb/Kconfig b/drivers/staging/uwb/Kconfig
> index 259e053e1e09..d9658c46686e 100644
> --- a/drivers/staging/uwb/Kconfig
> +++ b/drivers/staging/uwb/Kconfig
> @@ -3,6 +3,8 @@
>  # UWB device configuration
>  #
> 
> +
> +
>  menuconfig UWB
>         tristate "Ultra Wideband devices"
>         default n
> $ ./scripts/get_maintainer.pl x.patch
> Greg Kroah-Hartman <gregkh@linuxfoundation.org> (supporter:STAGING SUBSYSTEM,commit_signer:2/2=100%,authored:1/2=50%)
> Thomas Gleixner <tglx@linutronix.de> (commit_signer:1/2=50%,authored:1/2=50%)
> devel@driverdev.osuosl.org (open list:ULTRA-WIDEBAND (UWB) SUBSYSTEM:)
> linux-kernel@vger.kernel.org (open list)
> 
> 
> Am I missing something?



  reply	other threads:[~2019-08-08 11:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06 10:15 [PATCH] USB: Move wusbcore and UWB to staging as it is obsolete Greg Kroah-Hartman
2019-08-06 10:29 ` Joe Perches
2019-08-06 11:35   ` Greg Kroah-Hartman
2019-08-08  9:25     ` [PATCH] MAINTAINERS: mark wusbcore and UWB as obsolete Greg Kroah-Hartman
2019-08-08  9:41       ` Greg Kroah-Hartman
2019-08-08 11:15         ` Joe Perches [this message]
2019-08-08 11:23           ` Greg Kroah-Hartman
2019-08-08 16:09             ` 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=92ed89b0346a54fb06d3e08585a8d0b4175842f0.camel@perches.com \
    --to=joe@perches.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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).