From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [RESEND PATCH] drm/i915: do AUD_FREQ_CNTRL state save on all gen9+ platforms
Date: Tue, 14 Apr 2020 19:54:29 +0300 [thread overview]
Message-ID: <20200414165429.GC6112@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2004141315410.2957@eliteleevi.tm.intel.com>
On Tue, Apr 14, 2020 at 01:32:49PM +0300, Kai Vehmanen wrote:
> Hey,
>
> On Thu, 9 Apr 2020, Ville Syrjälä wrote:
>
> > On Thu, Apr 09, 2020 at 05:14:01PM +0300, Kai Vehmanen wrote:
> > > type of content free ping, but I still dare to seek your input on what is
> > > the proper way to get attention to a patch that are seemingly forever
> > > stuck on the review sideline.
> >
> > And what is this?
> > https://patchwork.freedesktop.org/patch/347148/?series=71527&rev=1
>
> that's a lost child I'm afraid. It's essentially the same patch I
> submitted late last year. It got review ok from Matt, and I thought it was
> going to be merged and went on to do other things -- i.e. I failed to
> follow-up on this. Back then I did not know about any actual bugs this
> would fix -- this was a generic change to align with hw specs.
>
> Fast forward two months. I had forgotten about that previous patch, and
> I ended up recreating the same patch to fix an actual bug. I.e. the of
> this thread:
> https://patchwork.freedesktop.org/series/74664/
OK. I sucked in the rb from the old patch and pushed the new version.
Thanks.
>
> I only very recently noticed the old patch. But alas, the new attempt
> is probably the one that should be merged as it has more information in
> the commit message (we now know about actual issues on JSL).
>
> > Just ping on original patch or ping someone on irc. Resending
> > the same patch over and over does no good. At least my brain just
> > ignores anything that looks like it's just a resend w/o any clear
> > justification.
>
> Ack, thanks a lot, this clarifies. In any case, patch author should own
> the follow-up and I definitely dropped the ball on the older #347148 .
>
> Br, Kai
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2020-04-14 16:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 14:44 [Intel-gfx] [RESEND PATCH] drm/i915: do AUD_FREQ_CNTRL state save on all gen9+ platforms Kai Vehmanen
2020-03-30 21:11 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: do AUD_FREQ_CNTRL state save on all gen9+ platforms (rev2) Patchwork
2020-03-31 8:25 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-04-09 14:14 ` [Intel-gfx] [RESEND PATCH] drm/i915: do AUD_FREQ_CNTRL state save on all gen9+ platforms Kai Vehmanen
2020-04-09 18:04 ` Ville Syrjälä
2020-04-14 10:32 ` Kai Vehmanen
2020-04-14 16:54 ` Ville Syrjälä [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=20200414165429.GC6112@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=kai.vehmanen@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 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.