<!-- Some styling for better description lists --><style type='text/css'>dt { font-weight: bold;float: left;display:inline;margin-right: 1em} dd { display:block; margin-left: 2em}</style>
***: ChanServ sets mode: +v mchehab
<br> hverkuil_ has left
<br> ChanServ sets mode: +v hverkuil
<br> ChanServ sets mode: +v mchehab
mchehab: Yesterday I finished handling the random patches that were pending... I skip several patches that would require a deeper review or seem to be handled by you
<br> did a few delegations to some camera-related drivers to sailus
<br> there are about 650 patches there, including the delegated ones
<br> we should try to reduce the backlog after the merge window... there are some *very* old patches there delegated to someone
pinchartl: <u>mchehab</u>: I plan to start with the uvcvideo backlog, I should have time for that next week
mchehab: that would be great!
<br> btd, did you have time to look at this patch series:
<br> [PATCH 00/13] Better handle pads for tuning/decoder part of the devices
pinchartl: not yet. I'm a bit late on a big deadline, I should be able to finish everything by the end of the week, then I can review patches
mchehab: ok
<br> if you can handle it on Monday, that would be great, as I'll add it for 4.19
***: services. sets mode: +o ChanServ
<br> ChanServ sets mode: +o mchehab
<br> mchehab sets mode: +q $~a
<br> ChanServ sets mode: -o mchehab
mchehab: finished setting the IRC channels we use
<br> now, #v4l-meeting and #media-maint has the same set of options
<br> on those channels, any registered people should be able to change the topic
<br> The options for #v4l and #linuxtv almost identical... the main difference is that topic changes require +t
<br> (with nobody has - so, in practice changing topic there requires OP permissions)
<br> all 4 channels are now registered (#v4l-meeting was not registered)
<br> I'm now owning 3 channels (the only one with a different owner is this channel)
<br> I guess I'll setup linuxtv to also log #v4l-meeting
<br> hmm... this channel has mode +t... only operators can change the topic
<br> we all can be operator here
<br> so, I guess this is fine
<br> at #v4l-meeting, I'm using -t
<br> the idea is that, if one uses it for a meeting, it can set the topic for the meeting if needed
<br> please always keep a message about the IRC logs at the topic
<br> hmm.. I guess I'll add it at the welcome message
<br> added a +g (free invite) to #v4l-meeting... Anybody in the channel may invite others (using the /invite command) to the channel.
<br> I guess we're all set with freenode configs - at least until the next spammers to start poping up
<br> I'll do a cleanup at the IRC logs to remove the traces from recent spam attacks
<br> logs filtered with:
<br> for i in *.log; do cat $i |grep -v "I thought you guys might be interested in" |grep -v "Read what IRC investigative journalists"|grep -v "A fascinating blog by freenode staff member"|grep -v "With our IRC ad service you can reach a global audience" >new/$i; done
<br> I guess that removed all traces from the last spam attack
pinchartl: <u>mchehab</u>: thank you for handling that
mchehab: anytime
pinchartl: <u>mchehab</u>: is there still time for one pull request for v4.19, given that v4.18 was delayed by a week, or is it too late ?
<br> it's a VSP1 patch series that introduces a new feature
<br> (support for interlaced video)
<br> it's not a big deal if it's too late
<br> but if there's still time, I'll send a pull request
mchehab: yeah, you can send a pull request...
pinchartl: thank you
mchehab: btw, there are 11 patches with SPDX stuff that you said you would be adding on your tree
pinchartl: yes
<br> I have
mchehab: (vsp1, if I stand correctly)
<br> feel free to send this also
pinchartl: have we reached a consensus on whether soc-camera should be touched or not ?
<br> <u>hverkuil</u>: how are we doing with the soc-camera removal ?
mchehab: let's add it
pinchartl: afaik there's no driver using it anymore
<br> is it just a matter of removing the #include in a few board files before it can be dropped ?
mchehab: if nothing, it would help documenting that the vendor is OK with spdx headers for it
<br> (as jacopo might have used some code from it on other patches with spdx)
pinchartl: <u>mchehab</u>: ok. +1 for Morimoto-san's patch count then :-)
<br> well, while soc-camera was initially started by Renesas, Guennadi contributed a lot too, so from that point of view maybe he should be asked if he's fine with it
<br> but I really don't think it matters much
mchehab: yeah, my main concern here is with companies, as they have a bunch of lawyers that could easily do some harm
<br> so, having them submitting licensing patches is always a good idea
<br> (submitting or endorsing)
<br> also, usually only companies would complain if a license text gets replaced by the equivalent SPDX tag
<br> engineers usually don't care if the SPDX tag says the same as the text :-)
pinchartl: have you heard of any company complaining ?
mchehab: yes
pinchartl: which one ?
mchehab: a german based dvb company... they want the license text to be kept
<br> they argued that german justice system is weird
<br> (they actually don't seem to be worried if *we* change the text, but they won't endorse - so *I* won't be merging such changes)
pinchartl: -_-'
mchehab: it seems that their main goal is to protect themselves from being sued in Germany
pinchartl: sued for what ?
mchehab: neither I or Greg was able to convince them otherwise
<br> I dunno... I guess it is just some paranoid behavior :-p
<br> s/was/were/
<br> a small company can easily be put out of business by too expensive lawsuits
<br> I didn't buy their arguments
<br> but they didn't buy mine either ;-)
hverkuil: <u>pinchartl</u>: I was planning to remove it for 4.20.
<br> (soc-camera)
pinchartl: <u>hverkuil</u>: ok
<br> finally :-)
hverkuil: <u>pinchartl</u>: no guarantees, it's not the highest prio thing on my list. But it would be nice it kill it.
pinchartl: sure
<br> there isn't much work left, right ?
hverkuil: Mostly some board files that still include soc_camera stuff, even though the corresponding soc-camera driver no longer exists.
<br> I need to make patches and collect Acks from the various maintainers.
pinchartl: <u>mchehab</u>: pull requests sent
<br> <u>hverkuil</u>: could we remove drivers/media/platform/soc_camera/ without waiting for the changes on the platform side ?
mchehab: thanks. will handle it probably later today... if not, will handle on Monday (need to do some internal reports today)
pinchartl: and then remove the headers from include/
<br> <u>mchehab</u>: no worries
<br> I've sent the VSP1 pull request I told you about, and the SPDX one
mchehab: OK
pinchartl: the SPDX patch series had two patches for DRM drivers, they're not included, I'll send them through Dave's tree
hverkuil: <u>pinchartl</u>: we could, but why the hurry?
pinchartl: <u>hverkuil</u>: there's no hurry indeed
<br> it would just feel good, that's all :-)
mchehab: yeah, sending DRM patches though Dave's tree is the right thing to do
<br> <u>pinchartl</u>: I feel good to know that this will be all gone on 4.20 :-D
<br> @all: please review and sign this patch if you agree:
<br> [PATCH] Documentation/media: uapi: Explicitly say there are no Invariant Sections
<br> this kind of change requires that major contributors to agree about it
<br> feel free to request others you find relevant to also add their SOB
<br> (in this specific case, I want SOB, and not acked or reviewed)
<br> I sent a similar request, via e-mail, to Gerd, to the Metzler brothers (dvb side) and to Johannes. Feel free to forward this request to other people you think it should also be signing it
***: mchehab has quit IRC (Ping timeout: 240 seconds)
<br> ChanServ sets mode: +v mchehab