From: Greg KH <gregkh@linuxfoundation.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: "Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Chris Wilson" <chris@chris-wilson.co.uk>,
"Jani Nikula" <jani.nikula@intel.com>,
stable <stable@vger.kernel.org>
Subject: Re: WTF: patch "[PATCH] drm/i915: Fix init_clock_gating for resume" was seriously submitted to be applied to the 4.14-stable tree?
Date: Mon, 4 Dec 2017 20:52:36 +0100 [thread overview]
Message-ID: <20171204195236.GA23720@kroah.com> (raw)
In-Reply-To: <CAKMK7uHeDm_7qteGgfTTHqO=QbvAwfOuzo6ki5Wyk0AD-bgJLw@mail.gmail.com>
On Mon, Dec 04, 2017 at 08:18:47PM +0100, Daniel Vetter wrote:
> On Mon, Dec 4, 2017 at 8:07 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Mon, Dec 04, 2017 at 10:45:50AM -0800, Rodrigo Vivi wrote:
> >> - What was the reason that you used the "WTF - never to be seen again" tone
> >> instead of the regular "FAILED - if someone wants to apply..."? Or in other
> >> words, what can we do to improve and not make you angry again?
> >
> > First off, the WTF is just an email script, don't take it personally.
>
> Jumping in here - tune it down a bit so it's less confusing? I guess
> in general it's not all that confusing, but since we did upset you
> rather badly a few months ago it's easy to jump to conclusions here
> and assume that i915 maintainers once more upset Greg badly :-/
Well, I'm ignoring the 10+ patches that I had to drop because I had
duplicates already applied, that did make me grumpy, but I'll live with
it for now...
> Just an idea in the spirit of the "make the bots friendlier"
> discussion from iirc kernel summit.
Normally, the script here is correct, it is rare that this type of
failure happens (dependancy on a patch that failed). In fact, I think
it's the first time...
thanks,
greg k-h
next prev parent reply other threads:[~2017-12-04 19:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 12:36 WTF: patch "[PATCH] drm/i915: Fix init_clock_gating for resume" was seriously submitted to be applied to the 4.14-stable tree? gregkh
2017-12-04 12:54 ` Ville Syrjälä
2017-12-04 13:13 ` Greg KH
2017-12-04 13:41 ` Ville Syrjälä
2017-12-04 13:47 ` Greg KH
2017-12-04 18:45 ` Rodrigo Vivi
2017-12-04 19:07 ` Greg KH
2017-12-04 19:18 ` Daniel Vetter
2017-12-04 19:52 ` Greg KH [this message]
2017-12-04 23:17 ` Rodrigo Vivi
2018-01-11 19:42 ` [PATCH stable-4.14 1/2] drm/i915: Move init_clock_gating() back to where it was Ville Syrjala
2018-01-11 19:42 ` [PATCH stable-4.14 2/2] drm/i915: Fix init_clock_gating for resume Ville Syrjala
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=20171204195236.GA23720@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=jani.nikula@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=stable@vger.kernel.org \
--cc=ville.syrjala@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;
as well as URLs for NNTP newsgroup(s).