From: Takashi Iwai <tiwai@suse.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: alsa-devel@alsa-project.org,
Lucas Tanure <tanureal@opensource.cirrus.com>,
patches@opensource.cirrus.com, Takashi Iwai <tiwai@suse.com>,
linux-kernel@vger.kernel.org,
Richard Fitzgerald <rf@opensource.cirrus.com>,
James Schulman <james.schulman@cirrus.com>,
David Rhodes <david.rhodes@cirrus.com>
Subject: Re: [PATCH v1 1/4] ALSA: hda: cs35l41: Improve dev_err_probe() messaging
Date: Tue, 12 Jul 2022 11:18:34 +0200 [thread overview]
Message-ID: <87ilo2r8np.wl-tiwai@suse.de> (raw)
In-Reply-To: <20220711095219.36915-1-andriy.shevchenko@linux.intel.com>
On Mon, 11 Jul 2022 11:52:16 +0200,
Andy Shevchenko wrote:
>
> Drop duplicate print of returned value in the messages and use pattern
> return dev_err_probe(...) where it's possible.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Applied this one, but postpone the rest three patches, as there seems
a build regression according 0day bot.
thanks,
Takashi
WARNING: multiple messages have this Message-ID (diff)
From: Takashi Iwai <tiwai@suse.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Lucas Tanure <tanureal@opensource.cirrus.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
James Schulman <james.schulman@cirrus.com>,
David Rhodes <david.rhodes@cirrus.com>,
Richard Fitzgerald <rf@opensource.cirrus.com>
Subject: Re: [PATCH v1 1/4] ALSA: hda: cs35l41: Improve dev_err_probe() messaging
Date: Tue, 12 Jul 2022 11:18:34 +0200 [thread overview]
Message-ID: <87ilo2r8np.wl-tiwai@suse.de> (raw)
In-Reply-To: <20220711095219.36915-1-andriy.shevchenko@linux.intel.com>
On Mon, 11 Jul 2022 11:52:16 +0200,
Andy Shevchenko wrote:
>
> Drop duplicate print of returned value in the messages and use pattern
> return dev_err_probe(...) where it's possible.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Applied this one, but postpone the rest three patches, as there seems
a build regression according 0day bot.
thanks,
Takashi
next prev parent reply other threads:[~2022-07-12 9:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 9:52 [PATCH v1 1/4] ALSA: hda: cs35l41: Improve dev_err_probe() messaging Andy Shevchenko
2022-07-11 9:52 ` Andy Shevchenko
2022-07-11 9:52 ` [PATCH v1 2/4] ALSA: hda: cs35l41: Allow compilation test on non-ACPI configurations Andy Shevchenko
2022-07-11 9:52 ` Andy Shevchenko
2022-07-12 4:38 ` kernel test robot
2022-07-12 4:38 ` kernel test robot
2022-07-11 9:52 ` [PATCH v1 3/4] ALSA: hda: cs35l41: Drop wrong use of ACPI_PTR() Andy Shevchenko
2022-07-11 9:52 ` Andy Shevchenko
2022-07-11 9:52 ` [PATCH v1 4/4] ALSA: hda: cs35l41: Consolidate selections under SND_HDA_SCODEC_CS35L41 Andy Shevchenko
2022-07-11 9:52 ` Andy Shevchenko
2022-07-12 9:18 ` Takashi Iwai [this message]
2022-07-12 9:18 ` [PATCH v1 1/4] ALSA: hda: cs35l41: Improve dev_err_probe() messaging Takashi Iwai
2022-07-12 10:01 ` Andy Shevchenko
2022-07-12 10:01 ` Andy Shevchenko
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=87ilo2r8np.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=david.rhodes@cirrus.com \
--cc=james.schulman@cirrus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.com \
--cc=tanureal@opensource.cirrus.com \
--cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.