#media-maint 2017-11-16,Thu

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)

WhoWhatWhen
***ChanServ sets mode: +v mchehab` [07:18]
................................. (idle for 2h43mn)
mchehabhi all [10:01]
syounghi [10:02]
mchehabhverkuil1, pinchartl, mkrufky, sailus: ping
from my side, the patches we had for -rc1 were merged
upstream
there are a few pull requests pending
[10:07]
hverkuil1mchehab: isn't the meeting in three hours? [10:09]
mchehabhmm.. I guess I miscalculated the TZ changes
it will me in 2 hours
sorry
(I subtracted one hour instead of adding one hour)
[10:10]
hverkuil1it's 11 am here, so 2 pm is in 3 hours. [10:11]
mchehabok, see you later at 12AM UTC
the scheduled time is 12AM UTC
https://www.timeanddate.com/worldclock/timezone/utc
[10:11]
hverkuil1It's winter time here, so that's 12 am UTC == 1 pm CET. Does Brazil have daylight saving time? (I guess not) [10:12]
mchehaba) weekly irc meetings to check on patch progress, and any issues
relating to that. Should also be used to point out patches that
need to be reviewed by other core devs (important to ensure others
are aware of such patches, don't assume they will magically see
them!).
Those meetings usually take place on Thursdays at 12 pm UTC
hverkuil1: we do
[10:14]
hverkuil1I don't mind moving the meeting to 1pm CET, but I'm not sure how it works for the others. [10:14]
mchehabwe're currently in daylight saving time
13AM UTC won't work for me
[10:14]
hverkuil1Oh, wait, it's summer for you, I forgot. [10:15]
mchehabyes
TZ changes at the opposite direction from EU ones
btw, US also had a TZ shift
that affects mkrufky
[10:15]
syoungI forgot about daylight savings too, I can't make 12.00 UTC. I can adjust my schedule for next onwards [10:17]
mchehabI don't object shifting it - but we likely need to discuss this with others
13:00 UTC won't work for me, though
as I have another meeting 13:30 UTC
(well, if we stick with just 30 mins, it could work, but I prefer to have a bigger slot - just in case we need to extend the meeting)
If we move it to be earlier, it will be harder for mkrufky
anyway, I'll start a thread at the ML
syoung: as you won't be here at 12 UTC, anything from your side?
[10:18]
mkrufky:-/ i happen to be awake, it's 5:20 am [10:21]
syoungnothing from my side. I haven't found much time to work on dvb stuff, which is unfortunate. [10:22]
mchehab:-)
just sent an email to submaintainers list in order to discuss what works best
mkrufky: I'm also an early bird
It is quite common for me to start working by 5am
[10:31]
mkrufky:-) im a little confused what time will the meeting be? 2.5 hours from now? or 1.5 hours from now? [10:32]
hverkuil11.5 [10:33]
mchehab1,5 hours from now
would that work for you?
[10:33]
mkrufkyok, 7am here
i can make it work :-)
[10:33]
mchehabok, good [10:33]
hverkuil1If you want me in a really nasty mood, then just wake me at 5am :-) [10:34]
mchehabsyoung: ok. let's try to organize the meeting for the next week, in a way that it would work for everybody [10:34]
mkrufkyah,. i see the email now too ... I *prefer* 8am as opposed to 7am
but 7am is ok with me
[10:34]
mchehab8am/13UTC would work for me, but only if it ends up to 13:30
on some past meetings, we end by using more than 30 mins
[10:36]
..... (idle for 24mn)
syoung11:00 to 16:00 UTC would be fine for me [11:00]
..... (idle for 24mn)
sailusHello! [11:24]
........ (idle for 37mn)
mchehabhi [12:01]
mkrufkyhello [12:01]
mchehabhi [12:04]
hverkuil1hi!
Let's just start, it looks like pinchartl missed the discussion.
[12:04]
mchehabok [12:05]
hverkuil1about the start time.
I don't have anything pending.
[12:06]
mchehabfrom the comments we heard so far, it seems that 12 UTC will work
so, except if commented otherwise at the ML, let's keep it
[12:07]
mkrufkywhat time is it now? 11UTC ? [12:07]
mchehab12UTC [12:07]
mkrufkyah [12:07]
mchehabhttps://www.timeanddate.com/worldclock/timezone/utc [12:08]
hverkuil1I posted an RFC patch series preparing the control framework for request support (needs more work, but should be sufficient for Alexandre to get basic codec support up and running). [12:09]
mkrufkyi tried to put that in the channel topic for easy reference next time, but..... (07:09:19 AM) You're not a channel operator [12:09]
mchehabdid you try to ask for OP priviledge to #chanserv? [12:10]
hverkuil1I'm planning to do some patch review tomorrow/Monday. [12:10]
mkrufkyi did not
(07:10:50 AM) ChanServ: (notice) You are not authorized to (de)op mkrufky on #media-maint.
[12:10]
mchehabyou should do something like /msg chanserv op #media-maint [12:11]
***ChanServ sets mode: +o mchehab [12:11]
mkrufkyi think an op has to op me [12:11]
***mchehab changes topic to: NEXT MEETINGS: at Thursdays 12:00 (UTC) - Use this channel only for media maintainership discussions. For everything else: #linuxtv (DVB only) or #v4l. Channel logs: https://linuxtv.org/irc/irclogger_log/media-maint [12:11]
mchehabthe channel was created by sailus [12:11]
mkrufkyi was going to add the link after the (UTC) before the `-` [12:12]
mchehabI guess only him can give privledges on chanserv [12:12]
mkrufkyno worries [12:12]
***mchehab changes topic to: MEETINGS at Thursdays 12:00 (UTC), except if otherwise discussed - Use this channel only for media maintainership discussions. For everything else: #linuxtv (DVB only) or #v4l. Channel logs: https://linuxtv.org/irc/irclogger_log/media-maint
ChanServ sets mode: -o mchehab
[12:13]
mchehabhverkuil1: I'll try to review it next week
as I said earlier today, our mass patch series was merged already upstream
I have one pending patch from syoung's tree to be merged (and another one coming), plus a patch series from sailus with bug fixes
I'll likely wait for -rc1 before submitting those
as Linus will be travelling on Sat
[12:15]
mkrufkyive been reviewing a huge patchset from brad that touches many many many drivers [12:17]
mchehabwhat it does? [12:17]
mkrufkyhe's making some cleanups and will post to the list soon
lots of card support and some bug fixes
[12:17]
mchehabok, good! [12:18]
mkrufkyhopefully he will be posting to the mailing list over the next week... its 20-25 patches or so [12:18]
mchehabnice to see him contributing with new card support [12:18]
mkrufkyyes im glad to see him touching kernel code now [12:18]
mchehabyep [12:19]
mkrufkypreviously he only worked in userspace ... so hauppauge + v4l has converted him to a new kernel dev :-)
its mostly DVB but some v4l stuff too.
[12:19]
hverkuil1mchehab: when you review the patch series be aware that it is just a first version and is missing some features (read the mail thread with Alexandre). And it's compile-tested only :-) [12:20]
mchehab:-) [12:20]
sailusHello all!
The day light saving time changes don't appear to be synchronised very well across the world. :-I
[12:20]
mchehab:-)
sailus: yeah, that can be a little bit cahotic
[12:21]
sailusmchehab: I have some fixes for 4.15, I'll send a pull request once we have the fixes branch ready. [12:21]
mchehabthat's why we should stick with UTC - as this doesn't change
(we can, of course, adjust the meeting time as needed - but let's always reference it to its UTC time)
sailus: OK
[12:21]
sailusI'm certainly fine with that... I've just gotten used to having the meeting an hour later. [12:22]
mchehaband I got used to have it one hour earlier :-)
I got confused with TZ changes this time, as BZ daylight saving happened while I was in Prague
s/BZ/TZ
[12:23]
mkrufkyi flew out of prague the day after the daylight savings, and it happened again the next week when i was in new york [12:24]
mchehabas usual, I'll wait for the end of the merge window to return my usual git pull request review [12:24]
mkrufkyas if jet lag doesnt already confuse the human body enough [12:24]
mchehabmkrufky: that can be really disturbing [12:24]
sailusIt was on Sunday morning in Finland (EU?), just a few hours after I arrived home. [12:26]
hverkuil1mchehab: BTW, I'll try to review the summit report today or tomorrow. [12:26]
mchehabthat trip was really weird... I went -6 hours (SFO time), then -2 hours (NYC - only scale) then PRG (+5) and NYC again with -1) - that together with a +1 TZ change in Brazil - in the middle
hverkuil1: good!
I'll try to do the same
[12:26]
hverkuil1I'll pay particular attention to the request API. [12:28]
sailusI'll read it, too. [12:29]
mchehabanything else?
(it is already 12:30 UTC - I would prefer if we could keep our meetings within the 30 mins length)
s/length/duration/
[12:29]
mkrufkyit so happens that either word is appropriate in this case :-) [12:30]
mchehabyeah, I was suspecting so [12:31]
............................................... (idle for 3h50mn)
***mchehab has left [16:21]
................................................................................... (idle for 6h54mn)
mkrufky has left [23:15]

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)