Multimedia-chat-meeting-2016-09-14

10:08 < pinchartl> topics for the day
10:08 < pinchartl> Topic 1. Status check for the multimedia tasks
10:08 < pinchartl> Topic 2. Additional tasks for Q4 2016
10:08 < pinchartl> Topic 3. Status update for Renesas on the multimedia todo list
10:08 < pinchartl> anything else ?
10:09 < pinchartl> maybe
10:09 < neg> yes a quick question about what work to aim to include for renesas-drivers releases
10:09 < pinchartl> Topic 4. Agenda for the multimedia face to face meeting in Berlin
10:09 < pinchartl> ok
10:10 < pinchartl> - Topic 1. Status check for the multimedia tasks
10:11 < pinchartl> in real alphabetical order today
10:11 < pinchartl> Kieran, you're first
10:11 < kbingham> hehe I feel privilidged :D
10:11 < pinchartl> (in the usual "what did I do, what do I plan to do, what problems do I have" format)
10:13 < kbingham> Since last meetinng, I have worked on VSP Partitioning Algorithm, now submitted and next plan a short task to assist geertu, as he has had to drop FDP1 from his tree. No particular problems at the moment.
10:14 < kbingham> Oh - actually - I do have a small problem.
10:14 < kbingham> Current tests still aren't running clean for me on the VSP. - So I'll see what that is  first.
10:15 < pinchartl> nice work on the VSP
10:15 < pinchartl> regarding the FDP, I've posted a v3 of the patches which you have reviewed (thanks for that)
10:15 < pinchartl> now that everything is in order I'll push my branch and will ask Geert to merge it
10:16 < pinchartl> so there's no need for you to get bothered with that
10:16 < kbingham> That's a good solution to assist Geert :D
10:16 < pinchartl> if you're now bored I have new tasks for you for Q4 which you could get started with :-)
10:16 < pinchartl> let's discuss them as part of the second topic
10:16 < kbingham> ;)
10:17 < pinchartl> regarding the VSP tests, which one(s) are failing for you ?
10:17 -!- morimoto [~user@relprex3.renesas.com] has joined #periperi
10:17 < pinchartl> hello Morimoto-san !
10:17 < kbingham> Test 1, 2, "yuv_to_rgbpnm: bad format"
10:17 < pinchartl> Geert was wondering if you were busy working on a new son :-D
10:18 < morimoto> sorry for my late
10:18 < morimoto> pinchartl: hehe :)
10:19 < pinchartl> kbingham: could you try to update raw2rgbpnm to the latest version ?
10:19 < kbingham> pinchartl: did something change there?
10:20 < pinchartl> "Add support for missing YUV 4:1:1, 4:2:0, 4:2:2 and 4:4:4 planar formats"
10:20 < pinchartl> that's not very recent though
10:20 < pinchartl> we can discuss this after the meeting
10:21 < kbingham> Yes, I dno't think this is topic for this meeting.
10:21 < pinchartl> and regarding your plan for the next two weeks, I assume you'll also write the VSP image partitioning task report for Jinzai, right ? :-)
10:21 < kbingham> Ah yes :)
10:21  * kbingham whistles loudly pretending he hadn't forgotten about that.
10:22 < pinchartl> thanks for the report
10:22 < pinchartl> next, me
10:22 < pinchartl> Since last meeting:
10:22 < pinchartl> - Posted v3 of the FDP driver
10:22 < pinchartl> - VSP image partitioning support
10:22 < pinchartl> - DU and VSP integration on H3
10:23 < pinchartl> For the next two weeks:
10:23 < pinchartl> - Continue working on the FDP driver to get it merged upstream
10:23 < pinchartl> - VIN and HDMI output patch review
10:23 < pinchartl> ah, I forgot to mention, I've also worked on
10:23 < pinchartl> - Rebased VSP HGO and HGT support
10:24 < kbingham> And ROT/FLIP
10:24 < pinchartl> yes, that's part of image partitioning, but it's worth mentioning it explicitly
10:25 < pinchartl> and, just for the fun of it, reverse-engineered the VSP RGB to HSV transformation to include emulation code in the test suite :-)
10:26 < pinchartl> morimoto: I forgot to reply to your e-mail, but less than 24h after you've told Niklas and me that the hardware team couldn't share the information because it was confidential, we managed to understand how it worked
10:26 < morimoto> pinchartl: we are sorry about that
10:27 < morimoto> Is it needed for test program, correct ?
10:28 < pinchartl> yes
10:28 < pinchartl> but it's fine now
10:28 < morimoto> OK
10:28 < pinchartl> we have fixed the problem, we know how it works
10:28 < pinchartl> we will have a similar issue with the UDS though:
10:28 < pinchartl> Issues and Blockers:
10:28 < pinchartl> - VSP test suite generates false positives in UDS testing
10:28 < pinchartl> This is caused by the emulation code scaling images with a method very different from the one used by the UDS, resulting in a need for a fuzzy comparison between the hardware output and the expected results with a too high threshold.
10:30 < pinchartl> in the next two weeks, I will also continue working on VSP HGO and HGT, as Mauro isn't convinced by the API proposal
10:30 < morimoto> About your "Issues and Blockers", do you need HW team help ?
10:31 < pinchartl> it would be nice to get more information about how the scaler operates, but I expect the same "this is confidential" answer :-/
10:31 < pinchartl> but it's worth asking
10:31 < pinchartl> this will likely be a task for the second half of Q4
10:31 < morimoto> OK, I will try, no expectation
10:32 < pinchartl> arigatō gozaimasu
10:32 < morimoto> Can you please add detail background on meeting report ?
10:32 < pinchartl> yes I will
10:32 < pinchartl> next, Morimoto-san
10:32 < morimoto> arigato
10:32 < morimoto> OK
10:33 < morimoto> I'm posting ALSA SoC patches to ML, but it seems Maintenor is focus to next kernel ?
10:33 < morimoto> so, nothing happen on my patches
10:33 < morimoto> I negotiated to Lars and Mark to discuss about ALSA SoC framework cleanup
10:34 < morimoto> and for new style ALSA SoC. I can talk it on ELCE timing
10:34 < morimoto> And BSP team is now focusing about Audio-DMAC power
10:34 < morimoto> As I asked on PeriPeriML, it is related to DMAEngine behavior
10:35 < pinchartl> please let me know if you would like me to join the discussion during ELCE
10:35 < morimoto> Thank. I'm happy if you can join to it.
10:35 < morimoto> it will be 2nd day, lunch timing
10:35 < morimoto> after Lars's presentation
10:36 < pinchartl> that works for me
10:36 < morimoto> About DMAEngine, rcar-dmac will power ON for Audio-DMAC when sound driver requests DMA channel
10:36 < morimoto> and power OFF when sound driver release it.
10:36 < morimoto> In my driver, it requests channel when .probe timing
10:37 < morimoto> this means, Audio DMAC is always ON
10:37 < pinchartl> right, I've seen your e-mail
10:37 < morimoto> which is correct approach
10:37 < morimoto> ?
10:37 < pinchartl> that's more of a core topic
10:37 < morimoto> Oops
10:37 < pinchartl> but in a nutshell, I think it would be good to optimize power consumption
10:37 < pinchartl> and only keep the hardware powered on when needed
10:38 < pinchartl> the issue there is that you need to call pm_runtime_get_sync() to power the hardware on
10:38 < pinchartl> which can't be called in atomic context
10:38 < pinchartl> and dma_async_issue_pending() needs to be callable in atomic context
10:38 < pinchartl> so to fix this we would likely need to extend the DMA engine API
10:39 < pinchartl> but to get sucha  change accepted
10:39 < pinchartl> we need to provide power consumption numbers
10:39 < morimoto> It is not Renesas specific issue, correct ?
10:39 < pinchartl> so we need to measure the extra power consumption caused by keeping the DMA engine powered on while not in use
10:39 < pinchartl> correct
10:40 < morimoto> Actually, I already created above patches. it request/release each times
10:40 < pinchartl> is that changes for the DMA engine driver or for the ALSA driver ?
10:40 < morimoto> Do you think I should post it to ML ? or keep it in my pocket ?
10:40 < morimoto> ALSA driver side only
10:40 < pinchartl> that's the second idea I was going to propose
10:41 < pinchartl> keep powering the DMA engine on in dma_request_channel()
10:41 < pinchartl> (or rather device_alloc_chan_resources())
10:41 < pinchartl> but move the dma_request_channel() from ALSA driver .probe() to a later point
10:41 < pinchartl> I think those patches would be sense to be posted
10:42 < morimoto> OK
10:42 < morimoto> This means, request/release happen many times. is this correct ?
10:43 < pinchartl> yes
10:43 < pinchartl> well, more than currently at leas
10:43 < pinchartl> t
10:43 < morimoto> OK. nice to know. I can be your father if you want :)
10:43 < pinchartl> I don't think my current father would be happy about that :-)
10:43 < morimoto> hehe :)
10:43 < morimoto> That's it from me
10:44 < pinchartl> what's your plan for the next two weeks ?
10:45 < morimoto> About patches, it is based on Maintenor.
10:45 < morimoto> I need to post more patches, but these are based on current patches.
10:45 < morimoto> If no update on ML, I will do Renesas side task
10:45 < pinchartl> ok
10:46 < pinchartl> thank you
10:46 < pinchartl> next, Niklas
10:46 < neg> a) Posted HGT patches, I see minimal work left to keep them up to date until they can be picked up
10:46 < neg> b) Start to work on VIN for M3 and rebase VIN Gen3 patches
10:46 < neg> c) No review on VIN Gen3 patches
10:47 < neg> also if there is time update the vsp-tests tool to take overlaping HGT hue areas in to account
10:47 < pinchartl> for the HGT, let's sync up on that after the meeting, I'll take your patches in my tree
10:47 < neg> ok
10:47 < pinchartl> I have done so already, probably a slightly different version, that's why we need to sync up
10:48 < pinchartl> regarding the VIN Gen3 patches, they were on my todo list after last meeting, but I had to focus on the VSP :-/
10:48 < pinchartl> I'll really try to get to them ASAP
10:48 < pinchartl> you had a quick question about what work to aim to include for renesas-drivers releases ?
10:49 < neg> np :-)
10:49 < neg> I have tried to keep the VIN Gen3 patches ready for renesas-drivers but have not always sucseeded in keeping them up to date. And since they seems to be a long way from beeing pickedup I was wondering if I should drop them from the patches I try to get in to renesas-drivers so Geert don't have to deal with any conflicts that series cause. If you see value in having them in renesas-drivers I will rejuvenate
10:49 < neg> my effort to keep them up to date at all times.
10:50 < pinchartl> geertu: any opinion on that ?
10:53 < pinchartl> renesas-drivers is a -next tree that is a bit more agressive than -next. it serves as a way to catch integration (as in merging multiple development branches) issues early
10:53 < pinchartl> including Gen3 VIN support in renesas-drivers is thus useful when you post a new version of the patch series
10:53 < pinchartl> but after that, if it starts generating painful conflicts, it likely means a new version of the series will be needed anyway
10:54 < pinchartl> so I wouldn't insist in keeping the code in renesas-drivers at all times
10:55 < neg> ok, I will continue to try and keep them up to date and included in renesas-drivers then
10:55 < pinchartl> please submit them for inclusion when you post a new version of the patches
10:55 < pinchartl> but don't spend an unnecessary large amount of time keeping them up-to-date between two versions
10:56 < neg> make sens
10:57 < pinchartl> thanks
10:57 < pinchartl> next, uli___ 
10:58 < uli___> a)
10:58 < uli___> - kept the salvator hdmi out alive (build failure; want to convert it to soc_device_match() before sending a new revision)
10:59 < uli___> - checked if it works without the funky cma reservation patch (it does, it's sufficient to increase the cma size)
10:59 < uli___> - started looking into gen2 vin integration in earnest (see c) )
10:59 < uli___> b) finish gen2 vin integration
10:59 < uli___> c) i don't have hardware docs for the gose board
10:59 < uli___> can somebody set me up with those?
10:59 < uli___> [that's it]
11:00 < pinchartl> do you regarding Gen2 VIN integration, that's due for the 18th, so I assume you'll finish it before two weeks ? :-)
11:00 < pinchartl> s/do you //
11:00 < uli___> yes
11:01 < pinchartl> thanks
11:02 < pinchartl> what's the status of DU,v4.9,public,ulrich,EDID generation support for the HDMI loopback test setup ?
11:02 < uli___> that's part of the hdmi in series, i'll send that out with gose support added before the due date
11:03 < pinchartl> perfect, thanks
11:03 < uli___> provided somebody can get me the docs...
11:03 < uli___> morimoto: HINT
11:03 < pinchartl> do you mean the schematics ?
11:03 < uli___> yes
11:03 < pinchartl> do you have a GPG key ?
11:03 < uli___> afraid not
11:04 < pinchartl> can you create one ? :-)
11:04 < uli___> is there an alternative? [i have no clue about that]
11:04 < pinchartl> morimoto: can I send the Gose schematics to Ulrich by e-mail without encryption ?
11:05 < morimoto> Hmm..
11:05 < morimoto> Now, it is under your NDA or export side issue
11:05 < morimoto> (I wonder why you have it ?)
11:05 < pinchartl> let's assume I don't have it :-)
11:05 < morimoto> Hehe :)
11:05 < morimoto> uli___: I will ask to Renesas guy
11:06 < uli___> thank you
11:06 < morimoto> but few availability
11:06 < pinchartl> availability of the schematics ?
11:07 < morimoto> maybe
11:07 < pinchartl> we're not asking for a board to be sent, just a document :-)
11:07 < morimoto> Hehe, OK
11:08 < pinchartl> thanks
11:08 < pinchartl> that's it for the status update
11:08 < pinchartl> Topic 2. Additional tasks for Q4 2016
11:09 < pinchartl> here are the additional tasks that will very likely be assigned to all of you for Q4
11:09 -!- Irssi: Pasting 7 lines to #periperi. Press Ctrl-K if you wish to do this or Ctrl-C to cancel.
11:09 < pinchartl> Laurent:
11:09 < pinchartl> - M3-W DU support (5 days)
11:09 < pinchartl> - LVDS mode selection for DU (5 days)
11:09 < pinchartl> Kieran:
11:09 < pinchartl> - DU write-back V4L2 prototype (10 days)
11:09 < pinchartl> - VSP image partitioning performance optimization (5 days)
11:10 -!- Irssi: Pasting 6 lines to #periperi. Press Ctrl-K if you wish to do this or Ctrl-C to cancel.
11:10 < pinchartl> Niklas:
11:10 < pinchartl> - M3-W VIN prototype support (5 days)
11:10 < pinchartl> Ulrich:
11:10 < pinchartl> - Audio loopback test program to test sampling rate and L-R issues (10 days)
11:10 < pinchartl> - DU Gen3 HDMI output upstream preparation (Channel 0 only) (5 days)
11:10 < pinchartl> I'll reach out to everybody with more detailed descriptions
11:10 < pinchartl> but if you already have questions, please go ahead
11:10 < morimoto> Is it updated version from Magnus ?
11:10 < pinchartl> (that's for the first half of Q4 only, the second half will follow later)
11:11 < morimoto> (I talked it with him, this morning)
11:11 < pinchartl> yes, that's from the e-mail he sent me a few hours ago
11:11 < morimoto> OK, nice to know
11:12 < morimoto> pinchartl: can you please add these tasks into peripelist todo list ?
11:12 < pinchartl> I will first write the detailed descriptions and get them approved, and I'll then add them to the todo list, sure
11:13 < morimoto> Thanks.
11:13 < pinchartl> Topic 3. Status update for Renesas on the multimedia todo list
11:14 < pinchartl> Morimoto-san told me that Renesas would like a status update on the following
11:14 -!- Irssi: Pasting 8 lines to #periperi. Press Ctrl-K if you wish to do this or Ctrl-C to cancel.
11:14 < pinchartl> DU,2016-12-31,request,?,M3
11:14 < pinchartl> DU,2016-06-30,request,ulrich,HDMI out ES1.1 support
11:14 < pinchartl> VSP,2016-06-30,request,laurent,solve UDS scaling regression for Gen3 
11:14 < pinchartl> VSP,2016-06-30,request,laurent,give information to Renesas about rotation status 
11:14 < pinchartl> VSP,2016-06-30,request,laurent,give information to Renesas about write-back feature plan
11:14 < pinchartl> VSP,2016-06-30,request,laurent,ES2.0 / M3 update
11:14 < pinchartl> VSP,2016-06-30,request,laurent,update request API on renesas-driver 
11:14 < pinchartl> VSP,2016-06-30,request,laurent,vsp1_pm_suspend() bugfix
11:14 < pinchartl> VSP,2016-10-30,request,laurent,VSP cache less support for BSP team
11:15 < morimoto> Yes, thanks. I will remove these if it was in todo list
11:15 < pinchartl> - DU,2016-12-31,request,?,M3
11:15 < pinchartl> there's an additional task for the first half of Q4
11:15 < pinchartl> - DU,2016-06-30,request,ulrich,HDMI out ES1.1 support
11:16 < pinchartl> Ulrich, any information about that ?
11:16 < uli___> not really. morimoto gave me info on how to implement that quite a while ago, but it does not seem to help
11:16 < uli___> morimoto: right?
11:16 < morimoto> Oops ?
11:17 < uli___> i mean, it still doesn't work on es1.1, right?
11:17 < morimoto> Ah, sorry, it was different story
11:17 < morimoto> My issue which was few weeks ago was my side fault
11:17 < morimoto> It was firmware issue.
11:18 < morimoto> So please forget it.
11:18 < uli___> that's good news :)
11:18 < morimoto> So, missing is only ES1.1 handling
11:18 -!- khiemnguyen [d2a0fca8@gateway/web/cgi-irc/kiwiirc.com/ip.210.160.252.168] has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
11:19 < morimoto> But it is related to Geert's ES handling magic ?
11:19 -!- khiemnguyen [d2a0fca8@gateway/web/cgi-irc/kiwiirc.com/ip.210.160.252.168] has joined #periperi
11:19 < uli___> yes, i'll look into that
11:19 < morimoto> OK. I will keep it under request file until next step
11:20 < pinchartl> uli___: do you think you can address that as part of either your base contract or the new "DU Gen3 HDMI output upstream preparation" task for Q4 ?
11:20 < uli___> yes, i think so
11:20 < morimoto> Nice to know !
11:20 < pinchartl> thank you
11:20 < pinchartl> - VSP,2016-06-30,request,laurent,solve UDS scaling regression for Gen3 
11:21 < pinchartl> - VSP,2016-06-30,request,laurent,give information to Renesas about rotation status
11:21 < pinchartl> this depends on image partitioning support that is now public
11:21 < pinchartl> both have been tested and are working
11:21 < pinchartl> - VSP,2016-06-30,request,laurent,give information to Renesas about write-back feature plan
11:21 < morimoto> OK. nice. I will remove these. But I can't find "UDS" word on todo list
11:22 < pinchartl> that's because there was nothing UDS-specific that had to be done
11:22 < pinchartl> implementing image partitioning fixed it
11:22 < morimoto> OK
11:22 < pinchartl> - VSP,2016-06-30,request,laurent,give information to Renesas about write-back feature plan
11:22 < pinchartl> will be assigned to Kieran as an additional task for the first half of Q4
11:23 < pinchartl> - VSP,2016-06-30,request,laurent,ES2.0 / M3 update
11:23 < pinchartl> will be handled as part of the DU M3 integration, assigned to me as an additional task for the first half of Q4
11:23 < pinchartl> - VSP,2016-06-30,request,laurent,update request API on renesas-driver
11:23 < morimoto> About, Write-back, it is next Kieran's task ?
11:23 < morimoto> I can remove it if todo list has it
11:23 < morimoto> correct ?
11:24 < pinchartl> please wait until the task get officially approved :-)
11:24 < morimoto> :) OK
11:24 < pinchartl> I'll then move it from the request file to the todo file
11:24 < pinchartl> - VSP,2016-06-30,request,laurent,update request API on renesas-driver
11:25 < pinchartl> I'll update the patch series before ELCE and send a pull request to Geert for renesas-drivers
11:25 < morimoto> you can handle only todo list, Renesas side will update request file
11:25 < pinchartl> (ok)
11:25 < pinchartl> my plan is to do so before kernel recipes, which is in two weeks in Paris
11:26 < pinchartl> but it might overflow to the week before ELCE
11:26 < pinchartl> at the latest it will be done before ELCE
11:26 < pinchartl> - VSP,2016-06-30,request,laurent,vsp1_pm_suspend() bugfix
11:26 < morimoto> Request API do you mean ?
11:26 < pinchartl> (yes)
11:26 < pinchartl> this has been proposed as an additional task for Q4, but Magnus told me that it needs to be discussed internally in Renesas first
11:26 < pinchartl> - VSP,2016-10-30,request,laurent,VSP cache less support for BSP team
11:27 < pinchartl> this has also been proposed as an additional task for Q4, and will possibly be accepted for the second batch
11:27 < pinchartl> it will be discussed face to face in Berlin first
11:27 < pinchartl> as it's not clear yet how to proceed
11:27 < morimoto> What is the problem about VSP1 PM suspen d?
11:27 < pinchartl> it doesn't work :-)
11:27 < pinchartl> suspend/resume is broken
11:27 < morimoto> Ahh OK
11:28 < pinchartl> it might even crash the kernel, I don't remember exactly
11:28 < morimoto> OK, thanks
11:28 < morimoto> And, I think I sent request about mising format something.
11:28 < morimoto> BSP team created local patch, do you remember ?
11:29 < pinchartl> here's the description of the problem I sent to Magnus
11:29 < pinchartl> The VSP suspend/resume code is known to be broken and needs to be fixed. This is further complicated by the fact that the VSP memory accesses are served by the FCP on Gen3, creating a suspend/resume dependency between the two devices.
11:29 < pinchartl> The VSP suspend/resume problem should be self-contained, but the FCP dependency would require dependencies support in the PM core. Work is ongoing in that area, and I believe we should take a more active role there. This isn't very suitable for additional tasks as they exist today as no deliverable can be guaranteed in a fixed amount of time.
11:29 < pinchartl> It might be possible to work around the problem by using the early/late suspend/resume handlers in the VSP and FCP drivers. I can't guarantee this at the moment without a more detailed and thus time-consuming analysis, hence the prototype status of this task.
11:30 < pinchartl> regarding the missing format
11:30 < pinchartl> was it the tri-planar formats for the DU ?
11:30 < morimoto> Maybe, I forgot detail
11:30 < pinchartl> so did I :-)
11:31 < pinchartl> but triplanar formats support has been merged
11:31 < morimoto> OK, nice
11:31 < pinchartl> any other question regarding the requests ?
11:32 < morimoto> nothing from me. Thanks
11:32 < pinchartl> you're welcome
11:32 < pinchartl> Topic 4. Agenda for the multimedia face to face meeting in Berlin
11:32 < pinchartl> we need to start drafting the agenda
11:32 < pinchartl> I'd like everybody to propose topics by e-mail in response to the chat report I will send
11:32 < pinchartl> and you can start now if you already have ideas in mind
11:33 < morimoto> I created Wiki page.
11:33 < morimoto> https://osdr.renesas.com/projects/linux-kernel-development/wiki/Miniperi-2016-10
11:33 < pinchartl> thank you
11:33 < kbingham> morimoto: Could I get an account to OSDR please?
11:34 < morimoto> Oopd, I will try. Please wait
11:34 < kbingham> np.
11:34 < morimoto> Maybe it will be after tomorrow
11:34 < pinchartl> morimoto: I think you can remove "What is the current status of "Rotation + ImagePertition" ?" and "Z-order" from the wiki page
11:34 < pinchartl> Z-order has been merged
11:34 < pinchartl> and patches for rotation + image partition have been posted yesterday
11:34 < morimoto> OK, but BSP team want to check it. keep it and set "finish" is help for me
11:35 < pinchartl> ok
11:35 < morimoto> s/help/helpful
11:35 < pinchartl> Topic 5. Next meeting
11:35 < neg> If possible I would like to talk about more pad aware v4l2 operations to you and Hans duinrg the mini multimedia summit (and to whom ever else is interessted ofc), but for periperi multimedia I think we talked about it in Tokyo
11:36 < pinchartl> neg: that's a good idea. could you propose that by e-mail to Hans ?
11:36 < neg> will do
11:37 < pinchartl> thanks
11:37 < pinchartl> I will attend Kernel Recipes in Paris in two weeks
11:37 < pinchartl> so I won't be available Wednesday-Friday
11:37 < pinchartl> and neither will I be available on Monday that week
11:38 < pinchartl> we could move the meeting to Tuesday, but that would conflict with the core meeting
11:38 < pinchartl> unless we move it one hour earlier, and keep it short
11:38 < pinchartl> another option is to hold the meeting on Wednesday without me
11:38 < pinchartl> thoughts ?
11:39 < morimoto> Wednesday = 28th ?
11:39 < pinchartl> yes
11:39 < neg> short meeting before core works for me, I think you should be in the meeting if possible
11:40 < pinchartl> given that it will be the last one before Berlin, I'd like to attend it, yes
11:40 < pinchartl> we'll keep the status update very short
11:40 < pinchartl> and focus on the agenda for the Berlin meeting
11:41 < pinchartl> so that would be 2016-09-27 at 08:00 BST / 09:00 CEST / 10:00 
11:41 < pinchartl> EEST / 16:00 JST
11:42 < neg> works for me
11:42 < morimoto> I booked
11:42 < uli___> ok
11:44 < pinchartl> thank you
11:44 < pinchartl> that's it for today
11:44 < pinchartl> thank you all for joinin