↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |
Who | What | When |
---|---|---|
*** | _franck__ has quit IRC (Ping timeout: 250 seconds) | [00:33] |
....................... (idle for 1h52mn) | ||
pinchartl has quit IRC (Ping timeout: 244 seconds) | [02:25] | |
...................................................................... (idle for 5h46mn) | ||
Renault | hverkuil: I'm the GS1662 driver developer, when you want to plan the meeting?
(hello all) | [08:11] |
.... (idle for 19mn) | ||
*** | DaRock has quit IRC (Quit: DaRock) | [08:30] |
....... (idle for 30mn) | ||
Renault | hverkuil: and, I'm in contact with another developper to add GS2972 which is very closed to GS1662 component | [09:00] |
............... (idle for 1h11mn) | ||
hverkuil | Renault: I am very, very busy I'm afraid. I'd also like to involve nohous in the discussion and he's not online. I have to wait until I see him here. The annoying thing is that I don't have nohous' email, otherwise we can arrange a date and time for a meeting via email.
Should you see him here before me, please ping him and ask for his email address. | [10:11] |
Renault | ok :) | [10:12] |
hverkuil | Realistically I won't have time this week. | [10:12] |
Renault | no problem, the next week I'm not here monday and friday (in case of the meeting will be planned the next week) | [10:13] |
.... (idle for 18mn) | ||
*** | aballier has quit IRC (Quit: leaving) | [10:31] |
pinchartl | hverkuil: I assume you won't have time to discuss my patch that adds a few new functions then ? | [10:44] |
hverkuil | pinchartl: ping me Friday. | [10:48] |
pinchartl | ok thanks
it's down to nitpicking now, it will be easier to handle it over e-mail sorry, I meant on IRC instead of over e-mail | [10:50] |
............................. (idle for 2h22mn) | ||
mchehab: ping | [13:13] | |
mchehab | pong | [13:15] |
pinchartl | how are you doing ? | [13:16] |
mchehab | fine, and you? | [13:16] |
pinchartl | I'm doing good, back from vacation, and tempted to leave again :-D
(I wish I could...) | [13:16] |
mchehab | :) | [13:17] |
pinchartl | I'm about to send you a pull request that includes two patches touching drivers/gpu/drm/rcar-du | [13:17] |
mchehab | mchehab doesn't know the meaning of vacations...
:-D | [13:17] |
pinchartl | Dave has acked them, he's fine with you merging them through your tree
I'll CC him on the pull request, is there anything else you'd like me to do ? | [13:17] |
mchehab | pinchartl: except if Linus sends a -rc8 or it is a serious bug fix, we're done for 4.7 merge window | [13:18] |
pinchartl | are we ? :-/ | [13:19] |
mchehab | yes | [13:19] |
pinchartl | those patches will generate conflict for v4.8
they've been out for some time now | [13:19] |
mchehab | why dave don't submit them? | [13:20] |
pinchartl | because they need to be submitted with corresponding V4L2 patches
for the VSP1 driver | [13:20] |
mchehab | let's then apply those after the merge window | [13:20] |
pinchartl | yes but they will conflict | [13:21] |
mchehab | ? | [13:21] |
pinchartl | there will be other patches for v4.8 on the KMS side
let me send the pull request, it will be easier to explain with the list of patches "[GIT PULL FOR v4.7] Renesas VSP updates" there's 13 patches the rcar-du-drm patches are number 11 and 12 they depend on previous vsp1 patches in the series | [13:21] |
mchehab | ok | [13:25] |
pinchartl | and patch 13 for the vsp1 driver further depend on them
they're thus sandwiched between vsp1 patches that's why Dave agreed to have them merged through your tree they don't conflict with anything queued in Dave's tree for v4.7 but it won't be true anymore for v4.8 as people are working on patches for v4.8 that will be merged through Dave's tree and will touch the rcar-du-drm driver | [13:25] |
mchehab | well, nothing prevents putting those things on a topic branch | [13:26] |
pinchartl | so we have an opportunity now to merge the patches without conflicts | [13:26] |
mchehab | and let both gpu and media branches depend on it | [13:26] |
pinchartl | I'd need a topic branch from you that Dave would then merge in his tree, on top of which he would need to merge my patches, and then create a topic branch for you that you would merge back to merge the last patch in the series
it's the back-and-forth that is messy if the dependency was in a single direction that's what I would have done why are we closed for v4.7 ? v4.6 hasn't been released yet | [13:27] |
mchehab | I mean, if we put this 13 patches on a topic branch, it won't be different than merging for 4.7
both gpu and media topic branches would be based on such "common" topic branch | [13:28] |
pinchartl | it would need to be merged by Dave before the current work in progress to avoid conflicts there
if the conflicting patches get merged in Dave's tree concurrently with the topic branch being merged in your tree we'll have conflicts when Linus will pull from you and Dave why are we closed for v4.7 ? | [13:28] |
mchehab | we close the week before rc7
to allow the Kernel genitors to review and submit fixes they made such request years ago, and we're doing such workflow for a while | [13:32] |
pinchartl | is that documented somewhere ? | [13:33] |
mchehab | there were some e-mails | [13:33] |
pinchartl | any chance for an exception ?
it's driver code only ;-) | [13:34] |
mchehab | still I use to remember people that submit late pull requests via IRC | [13:34] |
pinchartl | I would have submitted it last week but I was away
the patches were posted before that and I was waiting for review | [13:34] |
mchehab | last week I warned hverkuil that two of his pull requests would likely be delayed
due to that on IRC one is pure driver changes | [13:35] |
pinchartl | I'm fine with "likely" if it's not "certainly" ;-) | [13:36] |
hverkuil | mchehab: did the rcar-vin rewrite make the cut for 4.7? The others (cec framework, mediatek) were late so I'm not surprised they didn't make it. | [13:39] |
pinchartl | it hasn't been merged yet so I assume it's delayed too
mchehab: how will you synchronize with Dave for this if it can't be merged for v4.7 ? | [13:45] |
........... (idle for 54mn) | ||
mchehab | hverkuil: no, sorry. I got sick last week and was unable to handle it
I barely finished handling the individual patches for existing drivers | [14:41] |
.............. (idle for 1h8mn) | ||
pinchartl | mchehab: are you feeling better ? | [15:50] |
mchehab | still recovering
under medicine nothing serious... just a severe cold | [15:50] |
sailus: I think one of the VB2 fixes you wrote caused a regression for DVB | [16:07] | |
*** | benjiG has left | [16:07] |
mchehab | some change at __verify_planes_array
at videobuf2-v4l2.c maybe this patch commit 2c1f6951a8a82e6de0d82b1158b5e493fc6c54ab Author: Sakari Ailus <sakari.ailus@linux.intel.com> Date: Sun Apr 3 16:31:03 2016 -0300 [media] videobuf2-v4l2: Verify planes array in buffer dequeueing I'll revert and see if it solves the issue | [16:08] |
*** | egavinc has quit IRC (Quit: Leaving) | [16:22] |
mchehab | sailus: indeed it caused regressions at DVB
just sent a revert patch | [16:29] |
*** | stoth has quit IRC (Quit: stoth) | [16:34] |
.................. (idle for 1h28mn) | ||
awalls has left | [18:02] | |
...................................... (idle for 3h6mn) | ||
sailus | mchehab: Ping? | [21:08] |
mchehab | pong | [21:13] |
nohous | gleep | [21:14] |
sailus | I missed that pb could actually be NULL in some cases.
File I/O apparently as well besides DVB. So avoiding the check seems like the right thing to do. | [21:15] |
mchehab | sailus: for now, I'm just reverting it... it caused breakages on stable kernels
please prepare a next version and test it for all cases before re-submitting I discovered the bug by accident, just because I needed to test a DVB device and decided to rebase my test tree but people were already complaining about it at LKML | [21:23] |
sailus | I'll test file I/O but I have no convenient access to DVB devices.
I entirely missed DVB was using videobuf2-v4l2. | [21:28] |
headless | pinchartl: do you remember about the TCON patches?
oh, it's 0:30 again :-) | [21:31] |
.......................... (idle for 2h6mn) | ||
*** | kaspter has quit IRC (Remote host closed the connection) | [23:37] |
↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |