From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-sound@vger.kernel.org
Subject: Re: [PATCH 0/7] ALSA: Add missing module description
Date: Wed, 8 May 2024 12:45:57 +0300 [thread overview]
Message-ID: <ZjtJ1WOOmkSpEiLi@smile.fi.intel.com> (raw)
In-Reply-To: <ZjtHiq52po1kfZp2@smile.fi.intel.com>
On Wed, May 08, 2024 at 12:36:10PM +0300, Andy Shevchenko wrote:
> On Wed, May 08, 2024 at 11:11:19AM +0200, Takashi Iwai wrote:
> > Hi,
> >
> > here is a trivial patch series for adding the missing
> > MODULE_DESCRIPTION() to the code that can be built as modules
> > where make W=1 starts complaining the lack of MODULE_DESCRIPTION()
> > since recently.
> >
> > Fixes for ASoC follow later.
>
> Probably Reported-by: fits better, but I'm fine with either.
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
In case you decide to switch to Reported-by, replace also Link by Closes tag.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-05-08 9:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 9:11 [PATCH 0/7] ALSA: Add missing module description Takashi Iwai
2024-05-08 9:11 ` [PATCH 1/7] ALSA: ac97: legacy: " Takashi Iwai
2024-05-08 9:11 ` [PATCH 2/7] ALSA: ac97: bus: " Takashi Iwai
2024-05-08 9:11 ` [PATCH 3/7] ALSA: pcm_dmaengine: " Takashi Iwai
2024-05-08 9:11 ` [PATCH 4/7] ALSA: kunit: Add missing module descriptions Takashi Iwai
2024-05-08 9:11 ` [PATCH 5/7] ALSA: pcmtest: " Takashi Iwai
2024-05-09 8:56 ` Ivan Orlov
2024-05-08 9:11 ` [PATCH 6/7] ALSA: hda: cirrus_scodec_test: " Takashi Iwai
2024-05-08 9:11 ` [PATCH 7/7] sound: oss: dmasound: " Takashi Iwai
2024-05-08 9:17 ` [PATCH 0/7] ALSA: Add missing module description Dragan Simic
2024-05-08 9:36 ` Andy Shevchenko
2024-05-08 9:45 ` Andy Shevchenko [this message]
2024-05-09 8:13 ` Takashi Iwai
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=ZjtJ1WOOmkSpEiLi@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linux-sound@vger.kernel.org \
--cc=tiwai@suse.de \
/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