public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Sean Young <sean@mess.org>
Cc: "Michael Kerrisk (man-opages)" <mtk.manpages@gmail.com>,
	linux-man@vger.kernel.org, linux-media@vger.kernel.org,
	Alec Leamas <leamas.alec@gmail.com>
Subject: Re: [PATCH] lirc.4: remove ioctls and feature bits which were never implemented
Date: Thu, 12 Jul 2018 10:36:59 -0300	[thread overview]
Message-ID: <20180712103659.282c42e9@coco.lan> (raw)
In-Reply-To: <20180712132118.t5umg7z7qchpok7j@gofer.mess.org>

Em Thu, 12 Jul 2018 14:21:18 +0100
Sean Young <sean@mess.org> escreveu:

> On Thu, Jul 12, 2018 at 09:33:32AM -0300, Mauro Carvalho Chehab wrote:
> > Hi Michael/Alec,
> > 
> > Em Fri, 18 May 2018 16:25:29 +0100
> > Sean Young <sean@mess.org> escreveu:
> >   
> > > On Sun, May 06, 2018 at 12:34:53PM +0200, Michael Kerrisk (man-opages) wrote:  
> > > > [CCing original author of this page]
> > > > 
> > > > 
> > > > On 04/23/2018 12:26 PM, Sean Young wrote:    
> > > > > The lirc header file included ioctls and feature bits which were never
> > > > > implemented by any driver. They were removed in commit:
> > > > > 
> > > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d55f09abe24b4dfadab246b6f217da547361cdb6    
> > > > 
> > > > Alec, does this patch look okay to you?   
> > 
> > Sean is the sub-maintainer responsible for the LIRC code at the
> > media subsystem. He knows more about the current implementation
> > than anyone else, as he's working hard to improve it, and got
> > rid of all legacy LIRC drivers from staging (either fixing them
> > or removing the few ones nobody uses anymore).
> > 
> > As part of his work, some ioctls got removed, in order to make
> > the LIRC interface to match the real implementation.
> >    
> > > Mauro, as Alec is not responding, would you be able to sign this off?  
> > 
> > Most of the patch looks ok on my eyes. I noticed that some flags
> > still exists at include/uapi/linux/lirc.h:
> > 
> > 	LIRC_CAN_REC_RAW, LIRC_CAN_REC_PULSE, LIRC_CAN_SET_REC_FILTER
> > 	and LIRC_CAN_SEND_MODE2
> > 
> > Maybe instead of just removing, you would need to add some
> > explanation about them (or at the patch itself, explaining
> > why you're removing the descriptions for them).  
> 
> Those flags do still exist in the header file, we decided to keep them
> so that code does not suddenly fail to build. These flags either never
> had implementations or only had out-of-tree implementations. So, I do
> not think they belong in the man page.

Ok, makes sense to me.

Reviewed-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>

> 
> > > Alternatively, what can be done to progress this?
> > > 
> > > There is some new functionality in lirc which should be added to this man
> > > page too, so I have more to come (when I get round to writing it).  
> > 
> > Yeah, making it reflect upstream sounds the right thing to do.  
> 
> Absolutely, when kernel v4.18 is released there is more to add.
> 
> 
> Sean



Thanks,
Mauro

  reply	other threads:[~2018-07-12 13:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23 10:26 [PATCH] lirc.4: remove ioctls and feature bits which were never implemented Sean Young
2018-05-06 10:34 ` Michael Kerrisk (man-opages)
2018-05-18 15:25   ` Sean Young
     [not found]     ` <0c9ce46b-420e-6394-a40a-ca4de809c918@gmail.com>
2018-06-06 18:48       ` Sean Young
2018-07-12 12:33     ` Mauro Carvalho Chehab
2018-07-12 13:21       ` Sean Young
2018-07-12 13:36         ` Mauro Carvalho Chehab [this message]
2018-10-29 17:30         ` Sean Young
2018-10-29 18:47           ` Alec Leamas
2018-10-31  6:59 ` Michael Kerrisk (man-pages)

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=20180712103659.282c42e9@coco.lan \
    --to=mchehab+samsung@kernel.org \
    --cc=leamas.alec@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=sean@mess.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