All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: B K Karthik <bkkarthik@pesu.pes.edu>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Rob Herring <robh@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: mark usbvision as obsolete
Date: Sun, 2 Aug 2020 14:00:31 +0200	[thread overview]
Message-ID: <20200802120031.GB1289@bug> (raw)
In-Reply-To: <20200720031608.cujruuzsrfpnt7sh@pesu.pes.edu>

On Sun 2020-07-19 23:16:08, B K Karthik wrote:
> mark staging/media/usbvision as obsolete so
> checkpatch tells people not to send patches.

Umm... that's not right.

If we do not want people to fix it, it should not be in stagging -- it should 
be dropped.
									Pavel

> Signed-off-by: B K Karthik <bkkarthik@pesu.pes.edu> ---
>  MAINTAINERS | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index a88bf0759c90..82120c2fcedd 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -17946,7 +17946,7 @@ F:	include/uapi/linux/uvcvideo.h
>  USB VISION DRIVER
>  M:	Hans Verkuil <hverkuil@xs4all.nl>
>  L:	linux-media@vger.kernel.org
> -S:	Odd Fixes
> +S:	Odd Fixes / Obsolete
>  W:	https://linuxtv.org
>  T:	git git://linuxtv.org/media_tree.git
>  F:	drivers/staging/media/usbvision/
> -- 
> 2.20.1
> 



-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2020-08-02 12:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20  3:16 [PATCH] MAINTAINERS: mark usbvision as obsolete B K Karthik
2020-08-02 12:00 ` Pavel Machek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-07-19 18:04 bkkarthik
2020-07-19 23: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=20200802120031.GB1289@bug \
    --to=pavel@ucw.cz \
    --cc=bkkarthik@pesu.pes.edu \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.