| Message ID | 20221130141040.32447-1-arinc.unal@arinc9.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | remove label = "cpu" from DSA dt-binding | expand |
On Wed, Nov 30, 2022 at 05:10:35PM +0300, Arınç ÜNAL wrote: > Hello folks, > > With this patch series, we're completely getting rid of 'label = "cpu";' > which is not used by the DSA dt-binding at all. > > Information for taking the patches for maintainers: > Patch 1: netdev maintainers (based off netdev/net-next.git main) > Patch 2-3: SoC maintainers (based off soc/soc.git soc/dt) > Patch 4: MIPS maintainers (based off mips/linux.git mips-next) > Patch 5: PowerPC maintainers (based off powerpc/linux.git next-test) Hi Arınç So your plan is that each architecture maintainer merges one patch? That is fine, but it is good to be explicit, otherwise patches will fall through the cracks because nobody picks them up. I generally use To: to indicate who i expect to merge a patch, and everybody else in the Cc: Reviewed-by: Andrew Lunn <andrew@lunn.ch> Andrew
On 30.11.2022 18:55, Andrew Lunn wrote: > On Wed, Nov 30, 2022 at 05:10:35PM +0300, Arınç ÜNAL wrote: >> Hello folks, >> >> With this patch series, we're completely getting rid of 'label = "cpu";' >> which is not used by the DSA dt-binding at all. >> >> Information for taking the patches for maintainers: >> Patch 1: netdev maintainers (based off netdev/net-next.git main) >> Patch 2-3: SoC maintainers (based off soc/soc.git soc/dt) >> Patch 4: MIPS maintainers (based off mips/linux.git mips-next) >> Patch 5: PowerPC maintainers (based off powerpc/linux.git next-test) > > Hi Arınç > > So your plan is that each architecture maintainer merges one patch? Initially, I sent this series to soc@kernel.org to take it all but Rob said it must be this way instead. > > That is fine, but it is good to be explicit, otherwise patches will > fall through the cracks because nobody picks them up. I generally use > To: to indicate who i expect to merge a patch, and everybody else in > the Cc: Thanks for this, I'll follow suit if I don't see any activity for a few weeks. > > Reviewed-by: Andrew Lunn <andrew@lunn.ch> > > Andrew Arınç
I'm sending a more specific mail to make sure this series doesn't fall through the cracks like Andrew said. I'd like this merged this week before the merge window closes. Jakub, please take patch 1. Arnd, please take patch 2 and 3. Thomas, please take patch 4. Michael, please take patch 5. Arınç On 30.11.2022 17:10, Arınç ÜNAL wrote: > Hello folks, > > With this patch series, we're completely getting rid of 'label = "cpu";' > which is not used by the DSA dt-binding at all. > > Information for taking the patches for maintainers: > Patch 1: netdev maintainers (based off netdev/net-next.git main) > Patch 2-3: SoC maintainers (based off soc/soc.git soc/dt) > Patch 4: MIPS maintainers (based off mips/linux.git mips-next) > Patch 5: PowerPC maintainers (based off powerpc/linux.git next-test) > > I've been meaning to submit this for a few months. Find the relevant > conversation here: > https://lore.kernel.org/netdev/20220913155408.GA3802998-robh@kernel.org/ > > Here's how I did it, for the interested (or suggestions): > > Find the platforms which have got 'label = "cpu";' defined. > grep -rnw . -e 'label = "cpu";' > > Remove the line where 'label = "cpu";' is included. > sed -i /'label = "cpu";'/,+d arch/arm/boot/dts/* > sed -i /'label = "cpu";'/,+d arch/arm64/boot/dts/freescale/* > sed -i /'label = "cpu";'/,+d arch/arm64/boot/dts/marvell/* > sed -i /'label = "cpu";'/,+d arch/arm64/boot/dts/mediatek/* > sed -i /'label = "cpu";'/,+d arch/arm64/boot/dts/rockchip/* > sed -i /'label = "cpu";'/,+d arch/mips/boot/dts/qca/* > sed -i /'label = "cpu";'/,+d arch/mips/boot/dts/ralink/* > sed -i /'label = "cpu";'/,+d arch/powerpc/boot/dts/turris1x.dts > sed -i /'label = "cpu";'/,+d Documentation/devicetree/bindings/net/qca,ar71xx.yaml > > Restore the symlink files which typechange after running sed. > > Arınç ÜNAL (5): > dt-bindings: net: qca,ar71xx: remove label = "cpu" from examples > arm: dts: remove label = "cpu" from DSA dt-binding > arm64: dts: remove label = "cpu" from DSA dt-binding > mips: dts: remove label = "cpu" from DSA dt-binding > powerpc: dts: remove label = "cpu" from DSA dt-binding > >
Arınç ÜNAL <arinc.unal@arinc9.com> writes: > On 30.11.2022 18:55, Andrew Lunn wrote: >> On Wed, Nov 30, 2022 at 05:10:35PM +0300, Arınç ÜNAL wrote: >>> Hello folks, >>> >>> With this patch series, we're completely getting rid of 'label = "cpu";' >>> which is not used by the DSA dt-binding at all. >>> >>> Information for taking the patches for maintainers: >>> Patch 1: netdev maintainers (based off netdev/net-next.git main) >>> Patch 2-3: SoC maintainers (based off soc/soc.git soc/dt) >>> Patch 4: MIPS maintainers (based off mips/linux.git mips-next) >>> Patch 5: PowerPC maintainers (based off powerpc/linux.git next-test) >> >> Hi Arınç >> >> So your plan is that each architecture maintainer merges one patch? > > Initially, I sent this series to soc@kernel.org to take it all but Rob > said it must be this way instead. > >> >> That is fine, but it is good to be explicit, otherwise patches will >> fall through the cracks because nobody picks them up. I generally use >> To: to indicate who i expect to merge a patch, and everybody else in >> the Cc: > > Thanks for this, I'll follow suit if I don't see any activity for a few > weeks. IMHO the best solution if the patches are truly independent is to send them independantly to each maintainer. That way there's no confusion about whether someone else will take the series. It's also simpler for maintainers to apply a single standalone patch vs pick a single patch from a larger series. cheers
On 1.12.2022 13:42, Michael Ellerman wrote: > Arınç ÜNAL <arinc.unal@arinc9.com> writes: >> On 30.11.2022 18:55, Andrew Lunn wrote: >>> On Wed, Nov 30, 2022 at 05:10:35PM +0300, Arınç ÜNAL wrote: >>>> Hello folks, >>>> >>>> With this patch series, we're completely getting rid of 'label = "cpu";' >>>> which is not used by the DSA dt-binding at all. >>>> >>>> Information for taking the patches for maintainers: >>>> Patch 1: netdev maintainers (based off netdev/net-next.git main) >>>> Patch 2-3: SoC maintainers (based off soc/soc.git soc/dt) >>>> Patch 4: MIPS maintainers (based off mips/linux.git mips-next) >>>> Patch 5: PowerPC maintainers (based off powerpc/linux.git next-test) >>> >>> Hi Arınç >>> >>> So your plan is that each architecture maintainer merges one patch? >> >> Initially, I sent this series to soc@kernel.org to take it all but Rob >> said it must be this way instead. >> >>> >>> That is fine, but it is good to be explicit, otherwise patches will >>> fall through the cracks because nobody picks them up. I generally use >>> To: to indicate who i expect to merge a patch, and everybody else in >>> the Cc: >> >> Thanks for this, I'll follow suit if I don't see any activity for a few >> weeks. > > IMHO the best solution if the patches are truly independent is to send > them independantly to each maintainer. That way there's no confusion > about whether someone else will take the series. > > It's also simpler for maintainers to apply a single standalone patch vs > pick a single patch from a larger series. I agree. I'll do that next time. Cheers. Arınç