From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sasha Levin Subject: Re: [RESEND PATCH v2 1/2] drm/dp/mst: Reprobe EDID for MST ports on resume Date: Sat, 15 Jun 2019 18:38:09 -0400 Message-ID: <20190615223809.GS1513@sasha-vm> References: <20181024021925.27026-2-juston.li@intel.com> <20190614215644.8F9D821874@mail.kernel.org> <90274aca8c1b785caf9e3732e8b56e501e573a1f.camel@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Return-path: Content-Disposition: inline In-Reply-To: <90274aca8c1b785caf9e3732e8b56e501e573a1f.camel@redhat.com> Sender: stable-owner@vger.kernel.org To: Lyude Paul Cc: Juston Li , Lyude , intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, clinton.a.taylor@intel.com, stable@vger.kernel.org List-Id: intel-gfx@lists.freedesktop.org On Fri, Jun 14, 2019 at 06:10:20PM -0400, Lyude Paul wrote: >uh, Sasha not sure if you're a bot or not but this patch isn't even upstream This is indeed a bot, and that's indeed it's purpose :) We tend to get less responses if we wait for weeks for a patch to get upstream and queued for -stable because most often folks have moved on and forgotten all about it. This bot looks for commits tagged for stable, and runs basic sanity checks on them while they're still being discussed on the mailing list. This way we get more responses with instructions on how to deal with the patch. Either way, it won't be actually queued for stable before it's upstream.