mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Mark Brown <broonie@kernel.org>,
	linux-sound@vger.kernel.org,
	sound-open-firmware@alsa-project.org
Cc: "Bard Liao" <yung-chuan.liao@linux.intel.com>,
	"Daniel Baluta" <daniel.baluta@nxp.com>,
	"Jaroslav Kysela" <perex@perex.cz>,
	"Kai Vehmanen" <kai.vehmanen@linux.intel.com>,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	"Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>,
	"Pierre-Louis Bossart" <pierre-louis.bossart@linux.dev>,
	"Ranjani Sridharan" <ranjani.sridharan@linux.intel.com>,
	"Takashi Iwai" <tiwai@suse.com>,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org
Subject: Re: ASoC: SOF: topology: Use more common error handling code in sof_link_load()
Date: Wed, 1 Jul 2026 09:30:13 +0200	[thread overview]
Message-ID: <aa402cf5-6c7c-479b-ba0b-577ed10a3e3d@web.de> (raw)
In-Reply-To: <b04d8e4d-3d13-467b-841f-262204514377@sirena.org.uk>

>> Will the chances grow that further development ideas also from my change selection
>> can be integrated better?
> 
> Please don't send content free pings

How did you come to such a view after I dared to present reminders
for two concrete patches which can eventually be taken better into account
also by known patchwork interfaces?


>                                      and please allow a reasonable time
> for review.

Some years passed accordingly.


> Sending content free pings adds to the mail volume (if they are seen at
> all) which is often the problem and since they can't be reviewed
> directly if something has gone wrong you'll have to resend the patches
> anyway, so sending again is generally a better approach though there are
> some other maintainers who like them - if in doubt look at how patches
> for the subsystem are normally handled.
I hope that remaining development ideas can occasionally be handled in
more constructive ways.

Regards,
Markus

      reply	other threads:[~2026-07-01  7:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-17  7:56 [PATCH] " Markus Elfring
2026-06-30 11:27 ` Mark Brown
2026-06-30 17:08   ` Markus Elfring
2026-06-30 18:16     ` Mark Brown
2026-07-01  7:30       ` Markus Elfring [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=aa402cf5-6c7c-479b-ba0b-577ed10a3e3d@web.de \
    --to=markus.elfring@web.de \
    --cc=broonie@kernel.org \
    --cc=daniel.baluta@nxp.com \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=pierre-louis.bossart@linux.dev \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=sound-open-firmware@alsa-project.org \
    --cc=tiwai@suse.com \
    --cc=yung-chuan.liao@linux.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