public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	Sakari Ailus <sakari.ailus@iki.fi>,
	Sylwester Nawrocki <snawrocki@kernel.org>,
	Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [PATCHv2 1/5] media-device: set driver_version directly
Date: Fri, 21 Jul 2017 21:20:07 +0300	[thread overview]
Message-ID: <10142845.4VLkRYsldJ@avalon> (raw)
In-Reply-To: <aba5357e-5039-ed75-1ea1-1da76bfb6590@xs4all.nl>

Hi Hans,

On Friday 21 Jul 2017 13:06:38 Hans Verkuil wrote:
> On 21/07/17 12:57, Hans Verkuil wrote:
> > From: Hans Verkuil <hans.verkuil@cisco.com>
> > 
> > Don't use driver_version from struct media_device, just return
> > LINUX_VERSION_CODE as the other media subsystems do.
> > 
> > The driver_version field in struct media_device will be removed
> > in the following patches.
> > 
> > Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
> > ---
> > 
> >  drivers/media/media-device.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/drivers/media/media-device.c b/drivers/media/media-device.c
> > index fce91b543c14..7ff8e2d5bb07 100644
> > --- a/drivers/media/media-device.c
> > +++ b/drivers/media/media-device.c
> > @@ -71,7 +71,7 @@ static int media_device_get_info(struct media_device
> > *dev,> 
> >  	info->media_version = MEDIA_API_VERSION;
> 
> Related question about media_version: would it make sense to change this to
> LINUX_VERSION_CODE as well? This too has never been changed from when it was
> first introduced, making it pointless as a way for applications to detect
> when features were added.

Yes, I think it would make sense to do so.

> Unfortunately MEDIA_API_VERSION is defined in the public media.h header, but
> we can mark it unused. This define isn't documented in the spec, BTW.

We really went a long way since the first days of the media controller when it 
comes to API design. That being said, we still have a long way to go :-)

> >  	info->hw_revision = dev->hw_revision;
> > 
> > -	info->driver_version = dev->driver_version;
> > +	info->driver_version = LINUX_VERSION_CODE;
> > 
> >  	return 0;
> >  }

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2017-07-21 18:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-21 10:57 [PATCHv2 0/5] media: drop driver_version from media_device Hans Verkuil
2017-07-21 10:57 ` [PATCHv2 1/5] media-device: set driver_version directly Hans Verkuil
2017-07-21 11:06   ` Hans Verkuil
2017-07-21 18:20     ` Laurent Pinchart [this message]
2017-07-21 18:21   ` Laurent Pinchart
2017-07-21 10:57 ` [PATCHv2 2/5] s3c-camif: don't set driver_version Hans Verkuil
2017-07-22  6:52   ` Sylwester Nawrocki
2017-07-21 10:57 ` [PATCHv2 3/5] uvc: " Hans Verkuil
2017-07-21 10:57 ` [PATCHv2 4/5] atomisp2: " Hans Verkuil
2017-07-21 10:57 ` [PATCHv2 5/5] media-device: remove driver_version Hans Verkuil
2017-07-21 18:22   ` Laurent Pinchart
2017-07-22  6:52   ` Sylwester Nawrocki
2017-07-22 11:16   ` Sylwester Nawrocki
2017-07-22 11:31     ` Hans Verkuil

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=10142845.4VLkRYsldJ@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=hans.verkuil@cisco.com \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@iki.fi \
    --cc=snawrocki@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