From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH v1 1/1] ASoC: amd: acp: Remove (explicitly) unused header
Date: Tue, 26 Aug 2025 16:26:58 +0300 [thread overview]
Message-ID: <aK22Ik8KDFcKwCjc@smile.fi.intel.com> (raw)
In-Reply-To: <aKzD4EBSYb_RcWMO@finisterre.sirena.org.uk>
On Mon, Aug 25, 2025 at 09:13:20PM +0100, Mark Brown wrote:
> On Mon, Aug 25, 2025 at 07:01:36PM +0300, Andy Shevchenko wrote:
> > On Mon, Aug 25, 2025 at 04:45:17PM +0100, Mark Brown wrote:
>
> > > 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 truly believe the 5 month is reasonable time for review, no?
>
> You're missing the part about how you should resend instead.
Noted, thanks!
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2025-08-26 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 7:09 [PATCH v1 1/1] ASoC: amd: acp: Remove (explicitly) unused header Andy Shevchenko
2025-08-25 13:55 ` Andy Shevchenko
2025-08-25 15:45 ` Mark Brown
2025-08-25 16:01 ` Andy Shevchenko
2025-08-25 20:13 ` Mark Brown
2025-08-26 13:26 ` Andy Shevchenko [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=aK22Ik8KDFcKwCjc@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--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.