From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: B K KARTHIK PES2201800185STUDENT ECE DeptPESU EC Campus
<bkkarthik@pesu.pes.edu>,
devel@driverdev.osuosl.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH] staging: media: usbvision: removing prohibited space before ',' (ctx:WxW)
Date: Sat, 27 Jun 2020 10:49:32 +0200 [thread overview]
Message-ID: <20200627084932.GA1560170@kroah.com> (raw)
In-Reply-To: <f73c5a69-1bf9-d80d-2399-ef18ce78b8ac@xs4all.nl>
On Sat, Jun 27, 2020 at 10:28:31AM +0200, Hans Verkuil wrote:
> On 27/06/2020 07:07, Greg Kroah-Hartman wrote:
> >
> > A: http://en.wikipedia.org/wiki/Top_post
> > Q: Were do I find info about this thing called top-posting?
> > A: Because it messes up the order in which people normally read text.
> > Q: Why is top-posting such a bad thing?
> > A: Top-posting.
> > Q: What is the most annoying thing in e-mail?
> >
> > A: No.
> > Q: Should I include quotations after my reply?
> >
> > http://daringfireball.net/2007/07/on_top
> >
> > On Fri, Jun 26, 2020 at 11:42:49AM -0400, B K KARTHIK PES2201800185STUDENT ECE DeptPESU EC Campus wrote:
> >> Oh, I'm sorry but wouldn't it be helpful if we had a file that lists
> >> all drivers that are scheduled for removal?
> >
> > The TODO file in the directory for the driver should have this
> > information in it. I don't know if all of the media drivers have this,
> > if not, then there is no way you could have known this.
>
> They have, and in addition the Kconfig entry will mention that the driver
> is deprecated.
>
> TODO of usbvision:
>
> The driver is deprecated and scheduled for removal by the end
> of 2020.
>
> In order to prevent removal the following actions would have to
> be taken:
>
> - clean up the code
> - convert to the vb2 framework
> - fix the disconnect and free-on-last-user handling (i.e., add
> a release callback for struct v4l2_device and rework the code
> to use that correctly).
Ah, great, nevermind then!
B K, your wish is already granted, the text is present, you just needed
to have noticed it :)
greg k-h
next prev parent reply other threads:[~2020-06-27 8:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 14:32 [PATCH] staging: media: usbvision: removing prohibited space before ',' (ctx:WxW) B K Karthik
2020-06-26 14:36 ` Hans Verkuil
2020-06-26 14:47 ` Greg Kroah-Hartman
2020-06-26 15:42 ` B K KARTHIK PES2201800185STUDENT ECE DeptPESU EC Campus
2020-06-27 5:07 ` Greg Kroah-Hartman
2020-06-27 8:28 ` Hans Verkuil
2020-06-27 8:49 ` Greg Kroah-Hartman [this message]
2020-06-27 8:58 ` B K Karthik
2020-06-27 9:20 ` 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=20200627084932.GA1560170@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bkkarthik@pesu.pes.edu \
--cc=devel@driverdev.osuosl.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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.