From: Dave Jiang <dave.jiang@intel.com>
To: Jeff Johnson <quic_jjohnson@quicinc.com>,
Jonathan Cameron <Jonathan.Cameron@Huawei.com>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2] cxl: add missing MODULE_DESCRIPTION() macros
Date: Wed, 26 Jun 2024 09:41:27 -0700 [thread overview]
Message-ID: <73d13869-cb80-4226-b8fe-3e45fb7d2518@intel.com> (raw)
In-Reply-To: <aef7c12f-cefa-4823-b3a2-920c12990afa@quicinc.com>
On 6/26/24 9:02 AM, Jeff Johnson wrote:
> On 6/7/2024 7:10 AM, Jonathan Cameron wrote:
>> On Fri, 7 Jun 2024 06:57:15 -0700
>> Jeff Johnson <quic_jjohnson@quicinc.com> wrote:
>>
>>> make allmodconfig && make W=1 C=1 reports:
>>> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/cxl/core/cxl_core.o
>>> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/cxl/cxl_pci.o
>>> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/cxl/cxl_mem.o
>>> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/cxl/cxl_acpi.o
>>> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/cxl/cxl_pmem.o
>>> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/cxl/cxl_port.o
>>>
>>> Add the missing invocations of the MODULE_DESCRIPTION() macro.
>>>
>>> Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
>>
>> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>>
>> Thanks,
>
> Following up to see if anything else is needed from me. Hoping to see this in
> linux-next so I can remove it from my tracking spreadsheet :)
I have it locally queued, but will probably push to linux-next after rc6 drops.
>
> /jeff
next prev parent reply other threads:[~2024-06-26 16:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 13:57 [PATCH v2] cxl: add missing MODULE_DESCRIPTION() macros Jeff Johnson
2024-06-07 14:10 ` Jonathan Cameron
2024-06-26 16:02 ` Jeff Johnson
2024-06-26 16:41 ` Dave Jiang [this message]
2024-06-26 17:07 ` Jeff Johnson
2024-07-23 18:29 ` Jeff Johnson
2024-07-29 12:24 ` Ira Weiny
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=73d13869-cb80-4226-b8fe-3e45fb7d2518@intel.com \
--to=dave.jiang@intel.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_jjohnson@quicinc.com \
--cc=vishal.l.verma@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox