From: Petko Manolov <petko.manolov@konsulko.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org
Subject: Re: ovm6211 linux driver
Date: Fri, 3 Dec 2021 12:00:01 +0200 [thread overview]
Message-ID: <YanqoZ4xh+vtPIRM@karbon.home.net> (raw)
In-Reply-To: <63c9501c-6a58-ed69-265f-45f203952242@xs4all.nl>
On 21-12-03 10:55:15, Hans Verkuil wrote:
> On 03/12/2021 10:43, Hans Verkuil wrote:
> > Hi Petko,
> >
> > On 03/12/2021 10:08, Petko Manolov wrote:
> >> Hi guys,
> >>
> >> On request by certain company we've developed a media driver for
> >> OmniVision's ovm6211 camera sensor. We just got permission to mainline the
> >> code. How shall i proceed?
> >>
> >>
> >> cheers, Petko
> >>
> >
> > You found the correct mailinglist, so that's good :-)
> >
> > This is a good starting page:
> >
> > https://www.linuxtv.org/wiki/index.php/Developer_section
> >
> > Check the 'Kernel driver development' - 'Submitting Your Work:' links.
> >
> > Regards,
> >
> > Hans
> >
>
> Actually, this is a better source (for the media-subsystem-specific stuff):
>
> https://www.kernel.org/doc/html/latest/driver-api/media/maintainer-entry-profile.html
Thanks for the pointers. Perhaps i should have mentioned that i am already
maintaining several kernel drivers. This is my first 'media' driver and my
question was more in the lines of how you guys are doing it, although i did not
vocalize it explicitly. I assume the above link will give me the bits i still
don't know about.
I'll send the v0 patch shortly.
thanks,
Petko
next prev parent reply other threads:[~2021-12-03 10:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 9:08 ovm6211 linux driver Petko Manolov
2021-12-03 9:43 ` Hans Verkuil
2021-12-03 9:55 ` Hans Verkuil
2021-12-03 10:00 ` Petko Manolov [this message]
2021-12-03 9:43 ` Aw: " Robert Schlabbach
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=YanqoZ4xh+vtPIRM@karbon.home.net \
--to=petko.manolov@konsulko.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@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