Hi!

> Kindly be reminded to attend the weekly meeting through IRC to discuss
> technical topics with CIP kernel today. Our channel is the following:
> 
>     irc:irc.libera.chat:6667/cip
> 
> The IRC meeting is scheduled to UTC (GMT) 13:00:
> 
> https://www.timeanddate.com/worldclock/meetingdetails.html?year=2023&month=1&day=5&hour=13&min=0&sec=0&p1=224&p2=179&p3=136&p4=37&p5=241&p6=248
> 
> USWest    USEast    UK        DE        TW        JP
> 06:00     09:00     13:00     14:00     21:00     22:00

Sorry, I got confused and missed the meeting. I notice notes are at

https://ircbot.wl.linuxfoundation.org/meetings/cip/2023/01/cip.2023-01-05-13.02.log.html

so I'll go through them.

I did lot of reviews on 5.10.162 and 163. There is long series with

commit 466f98dac2f4908c8722b5fb23d0a1e481672f2c
Author: Jens Axboe <axboe@kernel.dk>
Date:   Thu Dec 22 14:30:11 2022 -0700

    io_uring: import 5.15-stable io_uring
    
    No upstream commit exists.
    
    This imports the io_uring codebase from 5.15.85, wholesale. Changes
    from that code base:
    
    - Drop IOCB_ALLOC_CACHE, we don't have that in 5.10.
    - Drop MKDIRAT/SYMLINKAT/LINKAT. Would require further VFS backports,
      and we don't support these in 5.10 to begin with.
    - sock_from_file() old style calling convention.
    - Use compat_get_bitmap() only for CONFIG_COMPAT=y
    
    Signed-off-by: Jens Axboe <axboe@kernel.dk>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

...which is 16000 lines of changes. There's no reasonable way to
review that. (And it probably has implications for 4.4 / 4.19).

I guess best way forward is to still take the patches even through we
can't review them, but if anyone is using io_uring (which I'd _not_
recommend at this moment), we might want to do some extra testing, or
get the users to test it.

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany