On 1/7/21 8:09 AM, Tom Rix wrote: > On 1/6/21 8:37 PM, Moritz Fischer wrote: >> This is a resend of the previous (unfortunately late) patchset of >> changes for FPGA DFL. > Is there something I can do to help ? > > I am paid to look after linux-fpga, so i have plenty of time. > > Some ideas of what i am doing now privately i can do publicly. > > 1. keep linux-fpga sync-ed to greg's branch so linux-fpga is normally in a pullable state. > > 2. an in-flight dev branch for the outstanding patches I have setup these branches based on Greg's char-misc-next fpga-next, which is char-misc-next base for fpga-testing fpga-testing, all the in-flight patches that would apply with automatic merge conflict resolution These are respectively https://github.com/trixirt/linux-fpga/tree/fpga-next https://github.com/trixirt/linux-fpga/tree/fpga-testing There are two trivial changes, that could go to 5.12 now. fpga: dfl: fme: Constify static attribute_group structs fpga: Use DEFINE_SPINLOCK() for spinlock respectively https://lore.kernel.org/linux-fpga/20210108235414.48017-1-rikard.falkeborn@xxxxxxxxx/ https://lore.kernel.org/linux-fpga/20201228135135.28788-1-zhengyongjun3@xxxxxxxxxx/ There are a couple of patchsets that conflict https://lore.kernel.org/linux-fpga/20210105230855.15019-7-russell.h.weight@xxxxxxxxx/ https://lore.kernel.org/linux-fpga/20201203171548.1538178-3-matthew.gerlach@xxxxxxxxxxxxxxx/ Which I will follow up on. And the xilinx patchset https://lore.kernel.org/linux-fpga/20201217075046.28553-1-sonals@xxxxxxxxxx/ Which is being split/worked on offline. If I have missed any patchset, poke me. Tom > > Tom > >
