All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Sugar Zhang <sugar.zhang@rock-chips.com>,
	ALSA-devel <alsa-devel@alsa-project.org>
Subject: Re: Rockchip I2S commit possibly ignored
Date: Tue, 16 Aug 2022 10:37:18 -0300	[thread overview]
Message-ID: <Yvudjkjxtv7M/DPL@geday> (raw)
In-Reply-To: <YvuZbrBWzRjHYQZj@sirena.org.uk>

On Tue, Aug 16, 2022 at 02:19:42PM +0100, Mark Brown wrote:
> On Tue, Aug 16, 2022 at 10:15:16AM -0300, Geraldo Nascimento wrote:
> 
> > I was looking at Rockchip I2S commits and it seems "ASoC: rockchip: i2s:
> > Reset the controller if soft reset failed" was supposed to have been
> > merged to your sound.git but never was. I don't know if this was
> > intentional or a real miss but in any case I'm letting you know.
> 
> Please don't send content free pings and please allow a reasonable time
> for review.  People get busy, go on holiday, attend conferences and so 
> on so unless there is some reason for urgency (like critical bug fixes)
> please allow at least a couple of weeks for review.  If there have been
> review comments then people may be waiting for those to be addressed.
> 
> 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.

This isn't my patch, it's a patch by Sugar Zhang from Rockchip that was
supposed to have been applied one year ago, give or take 10 days. I
can't resend a patch that wasn't authored by me.

Therefore I don't see the point of your complaint about "content free pings".

> 
> > However in the alsa-devel archives,
> > https://mailman.alsa-project.org/pipermail/alsa-devel/2021-August/189050.html
> > I see there was no commit info for the unmerged patch. Perhaps this
> > caused it to be black-holed?
> 
> If there was no commit info that means it wasn't applied.

That's what I thought. Cc:ing Sugar Zhang now.

  reply	other threads:[~2022-08-16 13:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16 13:15 Rockchip I2S commit possibly ignored Geraldo Nascimento
2022-08-16 13:19 ` Mark Brown
2022-08-16 13:37   ` Geraldo Nascimento [this message]
2022-08-16 15:22     ` Mark Brown
2022-08-16 15:46       ` Geraldo Nascimento
     [not found]       ` <YvvZzkYQ8Ce3/Lwj@geday>
2022-08-16 18:23         ` Mark Brown
2022-08-17  3:17         ` sugar zhang
2022-08-20 22:53           ` Geraldo Nascimento

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=Yvudjkjxtv7M/DPL@geday \
    --to=geraldogabriel@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=sugar.zhang@rock-chips.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.