All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, linux@armlinux.org.uk,
	linux-kernel@vger.kernel.org, o.rempel@pengutronix.de,
	p.zabel@pengutronix.de
Subject: Re: [PATCHv2 net-next 2/7] net: ag71xx: add MODULE_DESCRIPTION
Date: Fri, 6 Sep 2024 13:49:29 +0100	[thread overview]
Message-ID: <20240906124929.GG2097826@kernel.org> (raw)
In-Reply-To: <20240905194938.8453-3-rosenp@gmail.com>

On Thu, Sep 05, 2024 at 12:49:33PM -0700, Rosen Penev wrote:
> Now that COMPILE_TEST is enabled, it gets flagged when building with
> allmodconfig W=1 builds. Text taken from the beginning of the file.
> 
> Signed-off-by: Rosen Penev <rosenp@gmail.com>

Thanks,

This description lines-up with the one in Kconfig.

Reviewed-by: Simon Horman <horms@kernel.org>

  reply	other threads:[~2024-09-06 12:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05 19:49 [PATCHv2 net-next 0/7] various cleanups Rosen Penev
2024-09-05 19:49 ` [PATCHv2 net-next 1/7] net: ag71xx: add COMPILE_TEST to test compilation Rosen Penev
2024-09-05 19:49 ` [PATCHv2 net-next 2/7] net: ag71xx: add MODULE_DESCRIPTION Rosen Penev
2024-09-06 12:49   ` Simon Horman [this message]
2024-09-05 19:49 ` [PATCHv2 net-next 3/7] net: ag71xx: update FIFO bits and descriptions Rosen Penev
2024-09-05 19:49 ` [PATCHv2 net-next 4/7] net: ag71xx: use ethtool_puts Rosen Penev
2024-09-05 19:49 ` [PATCHv2 net-next 5/7] net: ag71xx: get reset control using devm api Rosen Penev
2024-09-05 19:49 ` [PATCHv2 net-next 6/7] net: ag71xx: remove always true branch Rosen Penev
2024-09-05 19:49 ` [PATCHv2 net-next 7/7] net: ag71xx: disable napi interrupts during probe Rosen Penev
2024-09-10  0:20 ` [PATCHv2 net-next 0/7] various cleanups patchwork-bot+netdevbpf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240906124929.GG2097826@kernel.org \
    --to=horms@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=p.zabel@pengutronix.de \
    --cc=pabeni@redhat.com \
    --cc=rosenp@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.