On Sat, 6 May 2023 00:28:05 +0000 SeongJae Park <sj@xxxxxxxxxx> wrote: > > That patch was merged into Linus's tree, so I assumed that's why it > > was dropped from mm-unstable. Perhaps I am wrong. > > Same to my assumption, and fit with the original mail's explanation. I > confirmed the patch has merged in the mainline as commit 96928d9032a7. So this > will be fixed if 1) mm-unstable is rebased on v6.4-rc1, 2) the dropped patch is > added again on mm-unstable, or 3) the patch[1] currently triggering the failure > is dropped. This is never an important issue for me, so I don't have any > preference or opinion about the fix. I just wanted to save time for others who > might got report of this. The mm-everything which I just pushed out has seq_buf_do_printk(). The mm-unstable branch doesn't, oops. I'll fix and repush.
