mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-kernel@vger.kernel.org, dan.carpenter@oracle.com,
	devel@driverdev.osuosl.org, shigekatsu.tateno@atmel.com,
	rupesh.gujare@atmel.com
Subject: Re: [PATCH 1/2] ozwpan: The maintainers are MIA, so orphan
Date: Mon, 10 Aug 2015 08:44:17 -0700	[thread overview]
Message-ID: <20150810154417.GA14033@kroah.com> (raw)
In-Reply-To: <1439214440-14461-1-git-send-email-Jason@zx2c4.com>

On Mon, Aug 10, 2015 at 03:47:19PM +0200, Jason A. Donenfeld wrote:
> Ozwpan is completely unmaintained and potentially a security problem. As
> this is a staging driver, it should be removed, since it has been
> abandoned. Marking it as orphaned is the first step here.
> 
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
> ---
>  MAINTAINERS | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 2d3d55c..0e14772 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -9717,7 +9717,7 @@ F:	drivers/staging/olpc_dcon/
>  
>  STAGING - OZMO DEVICES USB OVER WIFI DRIVER
>  M:	Shigekatsu Tateno <shigekatsu.tateno@atmel.com>
> -S:	Maintained
> +S:	Orphan
>  F:	drivers/staging/ozwpan/

As you are deleting the whole driver, this whole entry should be
removed as well, marking it "Orphan" doesn't mean anything after your
second patch.

Just do it all in one patch, that makes more sense.

thanks,

greg k-h

  parent reply	other threads:[~2015-08-10 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10 13:31 Ozwpan Driver: Removal Recommended Jason A. Donenfeld
2015-08-10 13:34 ` Jason A. Donenfeld
2015-08-10 13:47 ` [PATCH 1/2] ozwpan: The maintainers are MIA, so orphan Jason A. Donenfeld
2015-08-10 13:47   ` [PATCH 2/2] ozwpan: Remove from tree Jason A. Donenfeld
2015-08-10 15:44   ` Greg KH [this message]
2015-08-10 15:49     ` [PATCH] " Jason A. Donenfeld

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=20150810154417.GA14033@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Jason@zx2c4.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rupesh.gujare@atmel.com \
    --cc=shigekatsu.tateno@atmel.com \
    /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

Powered by JetHome