[...] > > > > > > Please route the set via bpf-next otherwise merge conflicts will be > > > severe. > > > > ack, fine > > > > in bpf-next the following two commits (available in net-next) are currently > > missing: > > - 632bb64f126a: net: mvneta: try to use in-irq pp cache in > > mvneta_txq_bufs_free > > - 879456bedbe5: net: mvneta: avoid possible cache misses in mvneta_rx_swbm > > > > is it ok to rebase bpf-next ontop of net-next in order to post all the > > series > > in bpf-next? Or do you prefer to post mvneta patches in net-next and bpf > > related changes in bpf-next when it will rebased ontop of net-next? > > bpf-next will receive these patches later today, > so I prefer the whole thing on top of bpf-next at that time.
sounds good, thx. Regards, Lorenzo
signature.asc
Description: PGP signature
