From: Mark Brown <broonie@kernel.org>
To: Geraldo Nascimento <geraldogabriel@gmail.com>
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 16:22:37 +0100 [thread overview]
Message-ID: <Yvu2PRrQvsRAJSm7@sirena.org.uk> (raw)
In-Reply-To: <Yvudjkjxtv7M/DPL@geday>
[-- Attachment #1: Type: text/plain, Size: 719 bytes --]
On Tue, Aug 16, 2022 at 10:37:18AM -0300, Geraldo Nascimento wrote:
> 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.
There's absolutely no problem with reposting someone else's patch - just
add your Signed-off-by at the end of the signoff chain.
> Therefore I don't see the point of your complaint about "content free pings".
In general the answer to "what's the status of this old patch?" is
almost always going to be the same so there's a form letter for it,
especially with such an old patch the chances of me having any
recollection of what's going on are minimal.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-08-16 15:23 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
2022-08-16 15:22 ` Mark Brown [this message]
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=Yvu2PRrQvsRAJSm7@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=geraldogabriel@gmail.com \
--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.