[AMD Official Use Only - General] > -----Original Message----- > From: Paolo Abeni <pabeni@xxxxxxxxxx> > Sent: Tuesday, June 14, 2022 2:40 PM > To: Pandey, Radhey Shyam <radhey.shyam.pandey@xxxxxxx>; > davem@xxxxxxxxxxxxx; edumazet@xxxxxxxxxx; kuba@xxxxxxxxxx; > robh+dt@xxxxxxxxxx; krzysztof.kozlowski+dt@xxxxxxxxxx; Katakam, Harini > <harini.katakam@xxxxxxx> > Cc: netdev@xxxxxxxxxxxxxxx; devicetree@xxxxxxxxxxxxxxx; linux- > kernel@xxxxxxxxxxxxxxx; git (AMD-Xilinx) <git@xxxxxxx> > Subject: Re: [PATCH v2 net-next] dt-bindings: net: xilinx: document xilinx > emaclite driver binding > > On Thu, 2022-06-09 at 22:23 +0530, Radhey Shyam Pandey wrote: > > Add basic description for the xilinx emaclite driver DT bindings. > > > > Signed-off-by: Radhey Shyam Pandey <radhey.shyam.pandey@xxxxxxx> > > Even if marked for 'net-next', my understanding is that should go via the > device tree repo. I'm dropping from the netdev patchwork, please correct me if > I'm wrong, thanks! I have seen a mixed set of the convention for dts patches. They are following both routes i.e device tree or subsystem repos provided acked from device tree maintainer. If there is preference for device tree repo then I can drop net-next from subject prefix and resend it for the dt repo. > > Paolo
