From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 2/3] ataflop: add missing MODULE_DESCRIPTION() macro
Date: Tue, 18 Jun 2024 09:40:53 +0200 [thread overview]
Message-ID: <CAMuHMdUrbM2nCJ7+hm8stsSBhRLMszyNKsiv1h2Z2CRJtzhcMg@mail.gmail.com> (raw)
In-Reply-To: <20240617-md-m68k-drivers-block-v1-2-b200599a315e@quicinc.com>
On Tue, Jun 18, 2024 at 3:14 AM Jeff Johnson <quic_jjohnson@quicinc.com> wrote:
> With ARCH=m68k, make allmodconfig && make W=1 C=1 reports:
> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/block/ataflop.o
>
> Add the missing invocation of the MODULE_DESCRIPTION() macro.
>
> Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2024-06-18 7:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 1:13 [PATCH 0/3] block: m68k: add missing MODULE_DESCRIPTION() macros Jeff Johnson
2024-06-18 1:13 ` [PATCH 1/3] amiflop: add missing MODULE_DESCRIPTION() macro Jeff Johnson
2024-06-18 7:41 ` Geert Uytterhoeven
2024-06-18 1:13 ` [PATCH 2/3] ataflop: " Jeff Johnson
2024-06-18 7:40 ` Geert Uytterhoeven [this message]
2024-06-18 1:13 ` [PATCH 3/3] z2ram: " Jeff Johnson
2024-06-18 7:41 ` Geert Uytterhoeven
2024-06-18 5:04 ` [PATCH 0/3] block: m68k: add missing MODULE_DESCRIPTION() macros Chaitanya Kulkarni
2024-06-19 13:54 ` Jens Axboe
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=CAMuHMdUrbM2nCJ7+hm8stsSBhRLMszyNKsiv1h2Z2CRJtzhcMg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=axboe@kernel.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_jjohnson@quicinc.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;
as well as URLs for NNTP newsgroup(s).