mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Eddie James <eajames@linux.ibm.com>, Jeremy Kerr <jk@ozlabs.org>,
	Joel Stanley <joel@jms.id.au>,
	Alistar Popple <alistair@popple.id.au>,
	Andrew Jeffery <andrew@codeconstruct.com.au>
Cc: <linux-fsi@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-aspeed@lists.ozlabs.org>,
	<kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH] fsi: add missing MODULE_DESCRIPTION() macros
Date: Tue, 9 Jul 2024 13:03:41 -0700	[thread overview]
Message-ID: <1f167dbf-9744-433c-aa5c-a35b66b79dde@quicinc.com> (raw)
In-Reply-To: <3edca7a4-361b-4381-8b13-70584a30e2b1@linux.ibm.com>

On 7/1/2024 8:00 AM, Eddie James wrote:
> 
> On 6/26/24 00:15, Jeff Johnson wrote:
>> On 6/5/2024 3:39 PM, Jeff Johnson wrote:
>>> make allmodconfig && make W=1 C=1 reports:
>>> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/fsi/fsi-core.o
>>> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/fsi/fsi-master-hub.o
>>> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/fsi/fsi-master-aspeed.o
>>> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/fsi/fsi-master-gpio.o
>>> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/fsi/fsi-master-ast-cf.o
>>> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/fsi/fsi-scom.o
>>>
>>> Add the missing invocations of the MODULE_DESCRIPTION() macro, and fix the
>>> copy/paste of the module description comment in fsi-master-ast-cf.c.
> 
> 
> Thanks!
> 
> Reviewed-by: Eddie James <eajames@linux.ibm.com>

I still don't see this in linux-next yet so following up again to see if
anything else is needed to get this merged.



      reply	other threads:[~2024-07-09 20:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 22:39 Jeff Johnson
2024-06-26  5:15 ` Jeff Johnson
2024-07-01 15:00   ` Eddie James
2024-07-09 20:03     ` Jeff Johnson [this message]

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=1f167dbf-9744-433c-aa5c-a35b66b79dde@quicinc.com \
    --to=quic_jjohnson@quicinc.com \
    --cc=alistair@popple.id.au \
    --cc=andrew@codeconstruct.com.au \
    --cc=eajames@linux.ibm.com \
    --cc=jk@ozlabs.org \
    --cc=joel@jms.id.au \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-fsi@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®