* [PATCH] net: lan743x: LAN743X selects FIXED_PHY to resolve a link error @ 2023-02-19 15:03 Tom Rix 2023-02-19 18:16 ` Simon Horman 0 siblings, 1 reply; 9+ messages in thread From: Tom Rix @ 2023-02-19 15:03 UTC (permalink / raw) To: davem, edumazet, kuba, pabeni, steen.hegelund Cc: netdev, linux-kernel, Tom Rix A rand config causes this link error drivers/net/ethernet/microchip/lan743x_main.o: In function `lan743x_netdev_open': drivers/net/ethernet/microchip/lan743x_main.c:1512: undefined reference to `fixed_phy_register' lan743x_netdev_open is controlled by LAN743X fixed_phy_register is controlled by FIXED_PHY So LAN743X should also select FIXED_PHY Signed-off-by: Tom Rix <trix@redhat.com> --- drivers/net/ethernet/microchip/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/net/ethernet/microchip/Kconfig b/drivers/net/ethernet/microchip/Kconfig index 24c994baad13..43ba71e82260 100644 --- a/drivers/net/ethernet/microchip/Kconfig +++ b/drivers/net/ethernet/microchip/Kconfig @@ -47,6 +47,7 @@ config LAN743X depends on PCI depends on PTP_1588_CLOCK_OPTIONAL select PHYLIB + select FIXED_PHY select CRC16 select CRC32 help -- 2.27.0 ^ permalink raw reply related [flat|nested] 9+ messages in thread
* Re: [PATCH] net: lan743x: LAN743X selects FIXED_PHY to resolve a link error 2023-02-19 15:03 [PATCH] net: lan743x: LAN743X selects FIXED_PHY to resolve a link error Tom Rix @ 2023-02-19 18:16 ` Simon Horman 2023-02-20 1:19 ` Andrew Lunn 0 siblings, 1 reply; 9+ messages in thread From: Simon Horman @ 2023-02-19 18:16 UTC (permalink / raw) To: Tom Rix Cc: davem, edumazet, kuba, pabeni, steen.hegelund, netdev, linux-kernel On Sun, Feb 19, 2023 at 10:03:21AM -0500, Tom Rix wrote: > A rand config causes this link error > drivers/net/ethernet/microchip/lan743x_main.o: In function `lan743x_netdev_open': > drivers/net/ethernet/microchip/lan743x_main.c:1512: undefined reference to `fixed_phy_register' > > lan743x_netdev_open is controlled by LAN743X > fixed_phy_register is controlled by FIXED_PHY > > So LAN743X should also select FIXED_PHY > > Signed-off-by: Tom Rix <trix@redhat.com> Hi Tom, I am a little confused by this. I did manage to cook up a config with LAN743X=m and FIXED_PHY not set. But I do not see a build failure, and I believe that is because when FIXED_PHY is not set then a stub version of fixed_phy_register(), defined as static inline in include/linux/phy_fixed.h, is used. Ref: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/tree/include/linux/phy_fixed.h?h=main&id=675f176b4dcc2b75adbcea7ba0e9a649527f53bd#n42 > --- > drivers/net/ethernet/microchip/Kconfig | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/net/ethernet/microchip/Kconfig b/drivers/net/ethernet/microchip/Kconfig > index 24c994baad13..43ba71e82260 100644 > --- a/drivers/net/ethernet/microchip/Kconfig > +++ b/drivers/net/ethernet/microchip/Kconfig > @@ -47,6 +47,7 @@ config LAN743X > depends on PCI > depends on PTP_1588_CLOCK_OPTIONAL > select PHYLIB > + select FIXED_PHY > select CRC16 > select CRC32 > help > -- > 2.27.0 > ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH] net: lan743x: LAN743X selects FIXED_PHY to resolve a link error 2023-02-19 18:16 ` Simon Horman @ 2023-02-20 1:19 ` Andrew Lunn 2023-02-20 6:46 ` Simon Horman 0 siblings, 1 reply; 9+ messages in thread From: Andrew Lunn @ 2023-02-20 1:19 UTC (permalink / raw) To: Simon Horman Cc: Tom Rix, davem, edumazet, kuba, pabeni, steen.hegelund, netdev, linux-kernel On Sun, Feb 19, 2023 at 07:16:07PM +0100, Simon Horman wrote: > On Sun, Feb 19, 2023 at 10:03:21AM -0500, Tom Rix wrote: > > A rand config causes this link error > > drivers/net/ethernet/microchip/lan743x_main.o: In function `lan743x_netdev_open': > > drivers/net/ethernet/microchip/lan743x_main.c:1512: undefined reference to `fixed_phy_register' > > > > lan743x_netdev_open is controlled by LAN743X > > fixed_phy_register is controlled by FIXED_PHY > > > > So LAN743X should also select FIXED_PHY > > > > Signed-off-by: Tom Rix <trix@redhat.com> > > Hi Tom, > > I am a little confused by this. > > I did manage to cook up a config with LAN743X=m and FIXED_PHY not set. > But I do not see a build failure, and I believe that is because > when FIXED_PHY is not set then a stub version of fixed_phy_register(), > defined as static inline in include/linux/phy_fixed.h, is used. > > Ref: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/tree/include/linux/phy_fixed.h?h=main&id=675f176b4dcc2b75adbcea7ba0e9a649527f53bd#n42 I'n guessing, but it could be that LAN743X is built in, and FIXED_PHY is a module? What might be needed is depends on FIXED_PHY || FIXED_PHY=n Andrew ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH] net: lan743x: LAN743X selects FIXED_PHY to resolve a link error 2023-02-20 1:19 ` Andrew Lunn @ 2023-02-20 6:46 ` Simon Horman 2023-02-21 2:29 ` Andrew Lunn 0 siblings, 1 reply; 9+ messages in thread From: Simon Horman @ 2023-02-20 6:46 UTC (permalink / raw) To: Andrew Lunn Cc: Tom Rix, davem, edumazet, kuba, pabeni, steen.hegelund, netdev, linux-kernel On Mon, Feb 20, 2023 at 02:19:34AM +0100, Andrew Lunn wrote: > On Sun, Feb 19, 2023 at 07:16:07PM +0100, Simon Horman wrote: > > On Sun, Feb 19, 2023 at 10:03:21AM -0500, Tom Rix wrote: > > > A rand config causes this link error > > > drivers/net/ethernet/microchip/lan743x_main.o: In function `lan743x_netdev_open': > > > drivers/net/ethernet/microchip/lan743x_main.c:1512: undefined reference to `fixed_phy_register' > > > > > > lan743x_netdev_open is controlled by LAN743X > > > fixed_phy_register is controlled by FIXED_PHY > > > > > > So LAN743X should also select FIXED_PHY > > > > > > Signed-off-by: Tom Rix <trix@redhat.com> > > > > Hi Tom, > > > > I am a little confused by this. > > > > I did manage to cook up a config with LAN743X=m and FIXED_PHY not set. > > But I do not see a build failure, and I believe that is because > > when FIXED_PHY is not set then a stub version of fixed_phy_register(), > > defined as static inline in include/linux/phy_fixed.h, is used. > > > > Ref: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/tree/include/linux/phy_fixed.h?h=main&id=675f176b4dcc2b75adbcea7ba0e9a649527f53bd#n42 > > I'n guessing, but it could be that LAN743X is built in, and FIXED_PHY > is a module? What might be needed is > > depends on FIXED_PHY || FIXED_PHY=n Thanks Andrew, LAN743X=y and FIXED_PHY=m does indeed produce the problem that Tom describes. And his patch does appear to resolve the problem. Unfortunately your proposed solution seems to run foul of a complex dependency situation. $ make ... drivers/net/ethernet/microchip/Kconfig:45:error: recursive dependency detected! drivers/net/ethernet/microchip/Kconfig:45: symbol LAN743X depends on FIXED_PHY drivers/net/phy/Kconfig:48: symbol FIXED_PHY depends on PHYLIB drivers/net/phy/Kconfig:16: symbol PHYLIB is selected by LAN743X For a resolution refer to Documentation/kbuild/kconfig-language.rst subsection "Kconfig recursive dependency limitations" ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH] net: lan743x: LAN743X selects FIXED_PHY to resolve a link error 2023-02-20 6:46 ` Simon Horman @ 2023-02-21 2:29 ` Andrew Lunn 2023-02-21 16:20 ` Simon Horman 0 siblings, 1 reply; 9+ messages in thread From: Andrew Lunn @ 2023-02-21 2:29 UTC (permalink / raw) To: Simon Horman Cc: Tom Rix, davem, edumazet, kuba, pabeni, steen.hegelund, netdev, linux-kernel On Mon, Feb 20, 2023 at 07:46:13AM +0100, Simon Horman wrote: > On Mon, Feb 20, 2023 at 02:19:34AM +0100, Andrew Lunn wrote: > > On Sun, Feb 19, 2023 at 07:16:07PM +0100, Simon Horman wrote: > > > On Sun, Feb 19, 2023 at 10:03:21AM -0500, Tom Rix wrote: > > > > A rand config causes this link error > > > > drivers/net/ethernet/microchip/lan743x_main.o: In function `lan743x_netdev_open': > > > > drivers/net/ethernet/microchip/lan743x_main.c:1512: undefined reference to `fixed_phy_register' > > > > > > > > lan743x_netdev_open is controlled by LAN743X > > > > fixed_phy_register is controlled by FIXED_PHY > > > > > > > > So LAN743X should also select FIXED_PHY > > > > > > > > Signed-off-by: Tom Rix <trix@redhat.com> > > > > > > Hi Tom, > > > > > > I am a little confused by this. > > > > > > I did manage to cook up a config with LAN743X=m and FIXED_PHY not set. > > > But I do not see a build failure, and I believe that is because > > > when FIXED_PHY is not set then a stub version of fixed_phy_register(), > > > defined as static inline in include/linux/phy_fixed.h, is used. > > > > > > Ref: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/tree/include/linux/phy_fixed.h?h=main&id=675f176b4dcc2b75adbcea7ba0e9a649527f53bd#n42 > > > > I'n guessing, but it could be that LAN743X is built in, and FIXED_PHY > > is a module? What might be needed is > > > > depends on FIXED_PHY || FIXED_PHY=n > > Thanks Andrew, > > LAN743X=y and FIXED_PHY=m does indeed produce the problem that Tom > describes. And his patch does appear to resolve the problem. O.K. So the commit message needs updating to describe the actual problem. > Unfortunately your proposed solution seems to run foul of a complex > dependency situation. I was never any good at Kconfig. Arnd is the expert at solving problems like this. You want either everything built in, or FIXED_PHY built in and LAN743X modular, or both modular. Andrew ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH] net: lan743x: LAN743X selects FIXED_PHY to resolve a link error 2023-02-21 2:29 ` Andrew Lunn @ 2023-02-21 16:20 ` Simon Horman 2023-02-26 15:15 ` Tom Rix 0 siblings, 1 reply; 9+ messages in thread From: Simon Horman @ 2023-02-21 16:20 UTC (permalink / raw) To: Andrew Lunn Cc: Tom Rix, davem, edumazet, kuba, pabeni, steen.hegelund, netdev, linux-kernel, Arnd Bergmann +Arnd On Tue, Feb 21, 2023 at 03:29:39AM +0100, Andrew Lunn wrote: > On Mon, Feb 20, 2023 at 07:46:13AM +0100, Simon Horman wrote: > > On Mon, Feb 20, 2023 at 02:19:34AM +0100, Andrew Lunn wrote: > > > On Sun, Feb 19, 2023 at 07:16:07PM +0100, Simon Horman wrote: > > > > On Sun, Feb 19, 2023 at 10:03:21AM -0500, Tom Rix wrote: > > > > > A rand config causes this link error > > > > > drivers/net/ethernet/microchip/lan743x_main.o: In function `lan743x_netdev_open': > > > > > drivers/net/ethernet/microchip/lan743x_main.c:1512: undefined reference to `fixed_phy_register' > > > > > > > > > > lan743x_netdev_open is controlled by LAN743X > > > > > fixed_phy_register is controlled by FIXED_PHY > > > > > > > > > > So LAN743X should also select FIXED_PHY > > > > > > > > > > Signed-off-by: Tom Rix <trix@redhat.com> > > > > > > > > Hi Tom, > > > > > > > > I am a little confused by this. > > > > > > > > I did manage to cook up a config with LAN743X=m and FIXED_PHY not set. > > > > But I do not see a build failure, and I believe that is because > > > > when FIXED_PHY is not set then a stub version of fixed_phy_register(), > > > > defined as static inline in include/linux/phy_fixed.h, is used. > > > > > > > > Ref: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/tree/include/linux/phy_fixed.h?h=main&id=675f176b4dcc2b75adbcea7ba0e9a649527f53bd#n42 > > > > > > I'n guessing, but it could be that LAN743X is built in, and FIXED_PHY > > > is a module? What might be needed is > > > > > > depends on FIXED_PHY || FIXED_PHY=n > > > > Thanks Andrew, > > > > LAN743X=y and FIXED_PHY=m does indeed produce the problem that Tom > > describes. And his patch does appear to resolve the problem. > > O.K. So the commit message needs updating to describe the actual > problem. Yes, that would be a good improvement. Perhaps a fixes tag too? > > Unfortunately your proposed solution seems to run foul of a complex > > dependency situation. > > I was never any good at Kconfig. Arnd is the expert at solving > problems like this. > > You want either everything built in, or FIXED_PHY built in and LAN743X > modular, or both modular. I _think_ the patch, which uses select FIXED_PHY for LAN743X, achieves that. I CCed Arnd in case he has any input. Though I think I read in an recent email from him that he is out most of this week. ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH] net: lan743x: LAN743X selects FIXED_PHY to resolve a link error 2023-02-21 16:20 ` Simon Horman @ 2023-02-26 15:15 ` Tom Rix 2023-02-27 8:37 ` Arnd Bergmann 2023-02-27 12:05 ` Simon Horman 0 siblings, 2 replies; 9+ messages in thread From: Tom Rix @ 2023-02-26 15:15 UTC (permalink / raw) To: Simon Horman, Andrew Lunn Cc: davem, edumazet, kuba, pabeni, steen.hegelund, netdev, linux-kernel, Arnd Bergmann On 2/21/23 8:20 AM, Simon Horman wrote: > +Arnd > > On Tue, Feb 21, 2023 at 03:29:39AM +0100, Andrew Lunn wrote: >> On Mon, Feb 20, 2023 at 07:46:13AM +0100, Simon Horman wrote: >>> On Mon, Feb 20, 2023 at 02:19:34AM +0100, Andrew Lunn wrote: >>>> On Sun, Feb 19, 2023 at 07:16:07PM +0100, Simon Horman wrote: >>>>> On Sun, Feb 19, 2023 at 10:03:21AM -0500, Tom Rix wrote: >>>>>> A rand config causes this link error >>>>>> drivers/net/ethernet/microchip/lan743x_main.o: In function `lan743x_netdev_open': >>>>>> drivers/net/ethernet/microchip/lan743x_main.c:1512: undefined reference to `fixed_phy_register' >>>>>> >>>>>> lan743x_netdev_open is controlled by LAN743X >>>>>> fixed_phy_register is controlled by FIXED_PHY >>>>>> >>>>>> So LAN743X should also select FIXED_PHY >>>>>> >>>>>> Signed-off-by: Tom Rix <trix@redhat.com> >>>>> Hi Tom, >>>>> >>>>> I am a little confused by this. >>>>> >>>>> I did manage to cook up a config with LAN743X=m and FIXED_PHY not set. >>>>> But I do not see a build failure, and I believe that is because >>>>> when FIXED_PHY is not set then a stub version of fixed_phy_register(), >>>>> defined as static inline in include/linux/phy_fixed.h, is used. >>>>> >>>>> Ref: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/tree/include/linux/phy_fixed.h?h=main&id=675f176b4dcc2b75adbcea7ba0e9a649527f53bd#n42 >>>> I'n guessing, but it could be that LAN743X is built in, and FIXED_PHY >>>> is a module? What might be needed is >>>> >>>> depends on FIXED_PHY || FIXED_PHY=n >>> Thanks Andrew, >>> >>> LAN743X=y and FIXED_PHY=m does indeed produce the problem that Tom >>> describes. And his patch does appear to resolve the problem. >> O.K. So the commit message needs updating to describe the actual >> problem. > Yes, that would be a good improvement. > > Perhaps a fixes tag too? > >>> Unfortunately your proposed solution seems to run foul of a complex >>> dependency situation. >> I was never any good at Kconfig. Arnd is the expert at solving >> problems like this. >> >> You want either everything built in, or FIXED_PHY built in and LAN743X >> modular, or both modular. > I _think_ the patch, which uses select FIXED_PHY for LAN743X, > achieves that. > > I CCed Arnd in case he has any input. Though I think I read > in an recent email from him that he is out most of this week. I was out last week as well :) I considered this a cleanup rather than a fix, I can add that fixes tag. From my point of view this is a linking problem, I don't mind changing, what commit message should I use ? Tom > ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH] net: lan743x: LAN743X selects FIXED_PHY to resolve a link error 2023-02-26 15:15 ` Tom Rix @ 2023-02-27 8:37 ` Arnd Bergmann 2023-02-27 12:05 ` Simon Horman 1 sibling, 0 replies; 9+ messages in thread From: Arnd Bergmann @ 2023-02-27 8:37 UTC (permalink / raw) To: Tom Rix, Simon Horman, Andrew Lunn Cc: David S . Miller, Eric Dumazet, Jakub Kicinski, Paolo Abeni, steen.hegelund, Netdev, linux-kernel On Sun, Feb 26, 2023, at 16:15, Tom Rix wrote: > On 2/21/23 8:20 AM, Simon Horman wrote: >> On Tue, Feb 21, 2023 at 03:29:39AM +0100, Andrew Lunn wrote: >>> On Mon, Feb 20, 2023 at 07:46:13AM +0100, Simon Horman wrote: >>>> >>>> LAN743X=y and FIXED_PHY=m does indeed produce the problem that Tom >>>> describes. And his patch does appear to resolve the problem. >>> O.K. So the commit message needs updating to describe the actual >>> problem. >> Yes, that would be a good improvement. >> >> Perhaps a fixes tag too? >> >>>> Unfortunately your proposed solution seems to run foul of a complex >>>> dependency situation. >>> I was never any good at Kconfig. Arnd is the expert at solving >>> problems like this. >>> >>> You want either everything built in, or FIXED_PHY built in and LAN743X >>> modular, or both modular. >> I _think_ the patch, which uses select FIXED_PHY for LAN743X, >> achieves that. >> >> I CCed Arnd in case he has any input. Though I think I read >> in an recent email from him that he is out most of this week. FWIW, the original patch looks good to me, Reviewed-by: Arnd Bergmann <arnd@arndb.de> I'm not sure if the #else path in include/linux/phy_fixed.h is actually helpful, as it does not avoid a link failure but just makes it less common. Maybe we should just drop that from the header and require all users of fixed_phy to 'select' that symbol even when they are built-in? Arnd ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH] net: lan743x: LAN743X selects FIXED_PHY to resolve a link error 2023-02-26 15:15 ` Tom Rix 2023-02-27 8:37 ` Arnd Bergmann @ 2023-02-27 12:05 ` Simon Horman 1 sibling, 0 replies; 9+ messages in thread From: Simon Horman @ 2023-02-27 12:05 UTC (permalink / raw) To: Tom Rix Cc: Andrew Lunn, davem, edumazet, kuba, pabeni, steen.hegelund, netdev, linux-kernel, Arnd Bergmann On Sun, Feb 26, 2023 at 07:15:01AM -0800, Tom Rix wrote: > > On 2/21/23 8:20 AM, Simon Horman wrote: > > +Arnd > > > > On Tue, Feb 21, 2023 at 03:29:39AM +0100, Andrew Lunn wrote: > > > On Mon, Feb 20, 2023 at 07:46:13AM +0100, Simon Horman wrote: > > > > On Mon, Feb 20, 2023 at 02:19:34AM +0100, Andrew Lunn wrote: > > > > > On Sun, Feb 19, 2023 at 07:16:07PM +0100, Simon Horman wrote: > > > > > > On Sun, Feb 19, 2023 at 10:03:21AM -0500, Tom Rix wrote: > > > > > > > A rand config causes this link error > > > > > > > drivers/net/ethernet/microchip/lan743x_main.o: In function `lan743x_netdev_open': > > > > > > > drivers/net/ethernet/microchip/lan743x_main.c:1512: undefined reference to `fixed_phy_register' > > > > > > > > > > > > > > lan743x_netdev_open is controlled by LAN743X > > > > > > > fixed_phy_register is controlled by FIXED_PHY > > > > > > > > > > > > > > So LAN743X should also select FIXED_PHY > > > > > > > > > > > > > > Signed-off-by: Tom Rix <trix@redhat.com> > > > > > > Hi Tom, > > > > > > > > > > > > I am a little confused by this. > > > > > > > > > > > > I did manage to cook up a config with LAN743X=m and FIXED_PHY not set. > > > > > > But I do not see a build failure, and I believe that is because > > > > > > when FIXED_PHY is not set then a stub version of fixed_phy_register(), > > > > > > defined as static inline in include/linux/phy_fixed.h, is used. > > > > > > > > > > > > Ref: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/tree/include/linux/phy_fixed.h?h=main&id=675f176b4dcc2b75adbcea7ba0e9a649527f53bd#n42 > > > > > I'n guessing, but it could be that LAN743X is built in, and FIXED_PHY > > > > > is a module? What might be needed is > > > > > > > > > > depends on FIXED_PHY || FIXED_PHY=n > > > > Thanks Andrew, > > > > > > > > LAN743X=y and FIXED_PHY=m does indeed produce the problem that Tom > > > > describes. And his patch does appear to resolve the problem. > > > O.K. So the commit message needs updating to describe the actual > > > problem. > > Yes, that would be a good improvement. > > > > Perhaps a fixes tag too? > > > > > > Unfortunately your proposed solution seems to run foul of a complex > > > > dependency situation. > > > I was never any good at Kconfig. Arnd is the expert at solving > > > problems like this. > > > > > > You want either everything built in, or FIXED_PHY built in and LAN743X > > > modular, or both modular. > > I _think_ the patch, which uses select FIXED_PHY for LAN743X, > > achieves that. > > > > I CCed Arnd in case he has any input. Though I think I read > > in an recent email from him that he is out most of this week. > > I was out last week as well :) :) > I considered this a cleanup rather than a fix, I can add that fixes tag. FWIIW, I'm happy with a cleanup. And in that chase there should be no fixes tag (conversely, if it is a fix, then there should be a fixes tag). As a cleanup, I suggest targeting this at net-next ([PATCH net-next]). As net-next is currently closed you'll need to wait for it to re-open. I expect that will happen next week, after v6.3-rc2 has been tagged. > From my point of view this is a linking problem, I don't mind changing, > what commit message should I use ? I think updating the patch description by adding something like "This problem occurs when LAN743X=y and FIXED_PHY=m." would be sufficient. ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2023-02-27 12:05 UTC | newest] Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2023-02-19 15:03 [PATCH] net: lan743x: LAN743X selects FIXED_PHY to resolve a link error Tom Rix 2023-02-19 18:16 ` Simon Horman 2023-02-20 1:19 ` Andrew Lunn 2023-02-20 6:46 ` Simon Horman 2023-02-21 2:29 ` Andrew Lunn 2023-02-21 16:20 ` Simon Horman 2023-02-26 15:15 ` Tom Rix 2023-02-27 8:37 ` Arnd Bergmann 2023-02-27 12:05 ` Simon Horman
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).