On Mon, 2 May 2022 11:33:18 +0800 "lipeifeng@xxxxxxxx" <lipeifeng@xxxxxxxx> wrote: > Hi Andrew： > > Thanks for your quick response. > > > They caused me some merge issues against mapletree, which I had > > resolved. Mapletree is dropped at present so I set these patches aside > > until the next version of the mapletree patches are available. > > Do we have a definite time for the next available version of the mapletree patches? I merged v2 a couple of days ago. It should be in mm-unstable then linux-next early next week. > Excuse me, is it possible for our patch to be independent of mapletree and brought in separately? Well, the changelog was rather unclear on the real-world end-user visible effects of the defect. When these prioritization decisions are to be made, it really helps to have a clear view of the impact to our users. > > > I've been holding your patches until Michel Lespinasse has had time to > > review them (and hopefully explain them to me ;)). Please review > > earlier comments which Michel has provided and ensure that those > > comments have been fully addressed so we can hopefully move forward on > > this. > > We will reply soon if Mr.Lespinasse provideds any advices or question. > And I haven't received any reply from Mr.Lespinasse yet, pls let me know > if i missed the reply. There was a big conference last week.
