public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Stefan Haberland <sth@linux.ibm.com>,
	Jan Hoeppner <hoeppner@linux.ibm.com>,
	Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	Sven Schnelle <svens@linux.ibm.com>
Cc: <linux-s390@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH] s390/dasd: add missing MODULE_DESCRIPTION() macros
Date: Tue, 16 Jul 2024 07:33:04 -0700	[thread overview]
Message-ID: <4bc3e19d-99eb-4004-a6ff-9ab9dc015cde@quicinc.com> (raw)
In-Reply-To: <c12b2289-aca5-4b2d-9599-e9ca8daa2003@linux.ibm.com>

On 7/16/2024 1:20 AM, Stefan Haberland wrote:
> Am 14.07.24 um 18:58 schrieb Jeff Johnson:
>> On 7/1/24 03:57, Stefan Haberland wrote:
>>> Am 16.06.24 um 04:19 schrieb Jeff Johnson:
>>>> With ARCH=s390, make allmodconfig && make W=1 C=1 reports:
>>>> WARNING: modpost: missing MODULE_DESCRIPTION() in 
>>>> drivers/s390/block/dasd_diag_mod.o
>>>> WARNING: modpost: missing MODULE_DESCRIPTION() in 
>>>> drivers/s390/block/dasd_eckd_mod.o
>>>> WARNING: modpost: missing MODULE_DESCRIPTION() in 
>>>> drivers/s390/block/dasd_fba_mod.o
>>>>
>>>> Add the missing invocations of the MODULE_DESCRIPTION() macro.
>>>>
>>>> Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
>>>> ---
>>>
>>> Applied, thanks.
>>>
>>
>> I still don't see this in linux-next. Does your tree feed into 
>> linux-next, or will it go into Linus' tree during the merge window?
>>
>> Hoping to have these warnings fixed tree-wide in 6.11
> 
> Sorry for the delay.
> 
> The DASD patches usually go upstream through the linux-block tree. I 
> have sent them yesterday and Jens already applied them.
> 

thanks!

      reply	other threads:[~2024-07-16 14:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-16  2:19 [PATCH] s390/dasd: add missing MODULE_DESCRIPTION() macros Jeff Johnson
2024-06-29  3:24 ` Jeff Johnson
2024-07-01 10:57 ` Stefan Haberland
2024-07-14 16:58   ` Jeff Johnson
2024-07-16  8:20     ` Stefan Haberland
2024-07-16 14:33       ` 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=4bc3e19d-99eb-4004-a6ff-9ab9dc015cde@quicinc.com \
    --to=quic_jjohnson@quicinc.com \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=hoeppner@linux.ibm.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=sth@linux.ibm.com \
    --cc=svens@linux.ibm.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