↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |
Who | What | When |
---|---|---|
syoung | mchehab: I'll look at it | [11:09] |
......... (idle for 44mn) | ||
mchehab: you're right, I missed this. | [11:53] | |
.......................... (idle for 2h9mn) | ||
mchehab: I've sent a patch. An alternate way of fixing this is to document LIRC_CAN_SEND_SCANCODE as unused.
what do you think, and do you think this should go into v4.16? | [14:02] | |
mchehab | removing it is a bad idea, as it could break userspace
if someone ever write something using LIRC_CAN_SEND_SCANCODE so, changing doc to say it is unused and deprecated seems a better idea no need to rush it to 4.16 | [14:04] |
syoung | LIRC_CAN_SEND_SCANCODE was introduced in v4.16, i.e. it did not exist in v4.15
so if it does go in, then it should go in v4.16 | [14:05] |
mchehab | huh? are we adding something to 4.16 that it is unused??? | [14:07] |
syoung | well, first it was added. Then after it was merged, I realised it broke lirc daemon. So it was removed again.
(merged to linuxtv/master) it's just a lirc feature bit, not essential at all, just for compatibility really. It tells you what ioctls will work, but you can just use the ioctls in the first place and see what they return | [14:09] |
mchehab | well, if everything happened for 4.16, we can remove it | [14:17] |
......... (idle for 40mn) | ||
syoung | should I create a fixes pull request for 4.16? | [14:57] |
I guess I should. | [15:10] | |
........ (idle for 35mn) | ||
*** | ChanServ sets mode: +v mchehab | [15:45] |
................................................. (idle for 4h3mn) | ||
ChanServ sets mode: +v mchehab | [19:48] | |
..... (idle for 24mn) | ||
ChanServ sets mode: +v mchehab | [20:12] |
↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |