| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |
| Who | What | When |
|---|---|---|
| *** | mchehab has quit IRC (*.net *.split)
sailus has quit IRC (*.net *.split) pinchartl has quit IRC (*.net *.split) syoung has quit IRC (*.net *.split) hverkuil has quit IRC (*.net *.split) hitchcock.freenode.net sets mode: +v hverkuil hitchcock.freenode.net sets mode: +v mchehab hitchcock.freenode.net sets mode: +v pinchartl | [04:04] |
| ................................................................. (idle for 5h22mn) | ||
| hverkuil | pinchartl: ping | [09:33] |
| ..................... (idle for 1h41mn) | ||
| pinchartl | hverkuil: pong | [11:14] |
| hverkuil | Hi Laurent! I have a few questions about the ti-vpe cal series:
1) Can you run v4l2-compliance for this device? Both video centric and MC centric (using the -m option). Just to check that there are no regressions compared to the current video centric driver. 2) Is there an affordable board that can be used to test this driver? | [11:15] |
| pinchartl | I've run v4l2-compliance, and there were no regressions. for the MC API there can't be any regression as it's new :-) | [11:17] |
| hverkuil | I'll also comment on two patches (57 and 73). Take a look at my comments (will post in a minute) and if you are OK with it, then I can make the change for you. | [11:18] |
| pinchartl | I can provide the output, but the project is on hold right now due to administrative issues, so it would have to wait a little bit
as for an affordable board, I don't think so I use the AM65x EVM and the DRA76x EVM they're not affordable | [11:18] |
| hverkuil | OK, you've run the compliance test for the video centric case, that's good enough for me.
It's actually patch 57 and 69 for which I have small comments. posted both comments. | [11:19] |
| pinchartl | I'll read that, thanks | [11:22] |
| hverkuil | If you are OK with those changes, then I would like to make a PR for patches 01-84. I prefer to wait one more week before I take the remainder of the series. | [11:23] |
| pinchartl: ah, OK, those changes you put in 57 and 69 are needed later. Never mind then, I'll take it as-is. It's a bit confusing when reviewing, but not worth the effort to change this. | [11:32] | |
| .... (idle for 17mn) | ||
| pinchartl | hverkuil: I've replied to both. they're valid points, but the code gets further reworked in the series, and both constructs that you pointed to as not needed would have to be added back. I'm not sure it's worth it removing them in 57 and 69 | [11:49] |
| ....... (idle for 32mn) | ||
| hverkuil | mchehab: you mentioned before that there was a limit to the number of patches in a PR, was that 50 or 100? And does patchwork check for that? Because I see that my PR for the 84-patch series doesn't appear in patchwork. If the limit is 50, then I'll have to split it up. | [12:21] |
| .......... (idle for 49mn) | ||
| mchehab: it looks like patchwork is not longer updating (that might be why I didn't see my PR). Can you check that it is receiving mails from the mailinglist? | [13:10] | |
| mchehab | patchwork doesn't have any limit
the limig is somewhere between 50 and 100 (don't remember the exact number) at the mailbomb script when someone pushes stuff at the git trees on linuxtv.org (the ones which generate notification e-mails) it affects only the notification e-mails | [13:18] |
| hverkuil | The real issue is that new emails do not seem to arrive in patchwork. | [13:20] |
| mchehab | e. g. the e-mails that go through linuxtv-commits@linuxtv.org
gah it means either 2 things: 1) patchwork got unsubscribed from vger; 2) vger rejected the e-mails (it may also be due to disk full) | [13:20] |
| hverkuil | They arrived fine in linux-media. | [13:22] |
| mchehab | no, it is not disk full | [13:22] |
| hverkuil | So not 2. | [13:22] |
| mchehab | it seems that it is working properly
this one is from today https://patchwork.linuxtv.org/patch/65372/ | [13:29] |
| hverkuil | I don't see '[PATCH v3] media: videobuf2: Print videobuf2 buffer state by name', nor do I see my PR: '[GIT PULL FOR v5.9] ti-vpe cleanups'
'[GIT PULL FOR v5.9] Various fixes' is the last thing I see in patchwork. https://patchwork.linuxtv.org/project/linux-media/list/ | [13:32] |
| mchehab | I don't see: videobuf2: Print videobuf2 buffer state by name
on my inbox can you find it on lore? https://lore.kernel.org/linux-media/ I can see it there but didn't arrived here yet forget it... local problem let me try to download it from lore and try to run the script which imports it | [13:34] |
| hverkuil | thanks! | [13:38] |
| .... (idle for 17mn) | ||
| mchehab | somehow, it is rejecting the e-mail from lore:
cat raw |./manage.py parsemail | echo "Rejected." Rejected. knowing why patchwork is rejececting something is hard btw, I even upgraded to the latest stable version, just in case | [13:55] |
| hverkuil | Do you want me to redirect the posts to you? See if that works? | [13:57] |
| mchehab | v2.1.4 -> v2.2.2
yeah, if you could send me a mbox file with all e-mails since the last merged patch (including it), it would be very helpful (or a maildir) the e-mails should be exactly identical to what patchwork is supposed to receive it works via .forward I'll add some prints at the python file which parses it (I used to have something like that in the past) | [13:58] |
| hverkuil | redirected 5 patches. Fingers crossed. | [14:00] |
| mchehab | just 5 files?
I need not only the patches, but also their replies as it will ignore everything that it is not patches, it is usually easy to just place everything starting from a timestamp on a file at the mbox format | [14:01] |
| hverkuil | I'll add a bunch of replies too...
redirected everything that came after "[GIT PULL FOR v5.9] Various fixes" | [14:02] |
| ..... (idle for 21mn) | ||
| mchehab | did you redirected them to patchwork@linuxtv.org?
$ cat raw |./manage.py parsemail Parsing mail loaded from stdin Duplicate mail for message ID %s <20200709174336.79112-1-ezequiel@collabora.com> well, patch is there already: https://patchwork.linuxtv.org/project/linux-media/patch/20200709174336.79112-1-ezequiel@collabora.com/ State Changes Requested your comment e-mails were also caught by patchwork ok, just manually imported one patch with: wget https://lore.kernel.org/linux-media/20200710131813.452513-2-paul.elder@ideasonboard.com/raw && cat raw |./manage.py parsemail patch went fine on patchwork: https://patchwork.linuxtv.org/project/linux-media/patch/20200710131813.452513-2-paul.elder@ideasonboard.com/ bouncing a patch to patchwork also worked fine https://patchwork.linuxtv.org/project/linux-media/patch/20200710131813.452513-1-paul.elder@ideasonboard.com/ hverkuil: the problem seems to be between vger and patchwork@linuxtv.org btw, not sure what happened, but my mailbox received lots of duplicated e-mail on my media ML inbox maybe some issue on vger? | [14:24] |
| hverkuil | Eh, that might be my mistake. I redirected the posts to you, not to patchwork.linuxtv.org. | [14:42] |
| mchehab | **** Address already subscribed to linux-media
vger has already it subscribed that's said, I found 2 issues on patchwork (besides the version upgrade): 1. the job that were supposed to answer e-mail were broken due to a bug at patchwork 2. there were some e-mails that were on hold at the server the server is set to take some time to handle mails in order to avoid some kinds of attacks anyway, both got fixed and the .forward rule restored It would be worth to rebounce those e-mails to patchwork@vger.kernel.org in case it lost something sending duplicate stuff won't hurt patchwork as it uses the message ID to avoid duplicaton | [14:56] |
| hverkuil | mchehab: you mean: rebounce to patchwork@linuxtv.org ? (instead of patchwork@vget.kernel.org) | [15:03] |
| mchehab | yes
that's what I meant ;-) just noticed I wrote the wrong address.... well, it is Friday ;-) mchehab needs to rest this was a stressful week | [15:03] |
| hverkuil | Done. | [15:04] |
| mchehab | thank you! | [15:04] |
| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |