From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D974BC433B4 for ; Tue, 18 May 2021 05:46:08 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id B625E61166 for ; Tue, 18 May 2021 05:46:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241109AbhERFrY (ORCPT ); Tue, 18 May 2021 01:47:24 -0400 Received: from new4-smtp.messagingengine.com ([66.111.4.230]:53211 "EHLO new4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234640AbhERFrY (ORCPT ); Tue, 18 May 2021 01:47:24 -0400 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailnew.nyi.internal (Postfix) with ESMTP id 80CC758123F; Tue, 18 May 2021 01:46:06 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Tue, 18 May 2021 01:46:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=Jbmf4WRhsfHsu1LE7NMnVkzakBi NS33xX0ldvnGydxc=; b=m5XlY1eLYX5EHnTiBxtOk4EshiYNVV3/JPAOwinAIwa Pc+bAQCoQtepYB796CC/fqOlyQOoh6RVY4sfO8iMzDSxZ+B4Hbclnh2GLi3s0+gO WRk1R+YxsNdmGADB1QsaRxUk+H9M7HXcVkFav54WBhPsT1PShI5TEgVLgh3x6bFJ XPsy5a5VUWHVah2NyrIdB6Jh3iMxhdY8H6pj6SyPNCYLAH7lr+5J2uE8YicjRWfb CpFGn2sx9lqNyJF2J9ocQxH1MgUzJb1Odm4bsPR+414gBKqr3UN7YxwJpBcX5RpU 4Y5B02nDdGgp3XrJRBZpxf2ZDkLEt4UQAUifDmoyB7g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=Jbmf4W RhsfHsu1LE7NMnVkzakBiNS33xX0ldvnGydxc=; b=U3ykAomG81+5MrN9HJXlfm Muv1aJdWzVZ1O9GppD6WDRH9LNKMcLpSDSup24DRIxsmAJ+4qPWy81Kut8VErFtP DPLteZbxv/Vn9DcAs5zJyR/NSU6HaOWMTLMBTr/HIRbWdHBEK7IvhMPjWNx5LM3W OyKb1kSiYsH37IWAGCdt3MjAh270GR+SusI/U6LdJf5adKXYmfyeuRVE0bb3LXzz NplM5kt7wJVAC3BY8gCrwClfNks8r26aTPUpfbz6CBDcGYyKZKPAdxNol+/1lLdP o+MNWONlm4JqyzyR5iXOIJ6MVE5Tf6e0WdpZhrqa00POdryO4lYPNOHvaanF2M2g == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvdeiiedgleegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpefirhgvghcu mffjuceoghhrvghgsehkrhhorghhrdgtohhmqeenucggtffrrghtthgvrhhnpeevueehje fgfffgiedvudekvdektdelleelgefhleejieeugeegveeuuddukedvteenucfkphepkeef rdekiedrjeegrdeigeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehgrhgvgheskhhrohgrhhdrtghomh X-ME-Proxy: Received: from localhost (83-86-74-64.cable.dynamic.v4.ziggo.nl [83.86.74.64]) by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 18 May 2021 01:46:05 -0400 (EDT) Date: Tue, 18 May 2021 07:45:59 +0200 From: Greg KH To: Linus Torvalds Cc: Sasha Levin , Linux Kernel Mailing List , stable , Tetsuo Handa , syzbot , dri-devel , Linux Fbdev development list Subject: Re: [PATCH AUTOSEL 5.12 5/5] tty: vt: always invoke vc->vc_sw->con_resize callback Message-ID: References: <20210518010940.1485417-1-sashal@kernel.org> <20210518010940.1485417-5-sashal@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-fbdev@vger.kernel.org On Mon, May 17, 2021 at 06:35:24PM -0700, Linus Torvalds wrote: > On Mon, May 17, 2021 at 6:09 PM Sasha Levin wrote: > > > > From: Tetsuo Handa > > > > [ Upstream commit ffb324e6f874121f7dce5bdae5e05d02baae7269 ] > > So I think the commit is fine, and yes, it should be applied to > stable, but it's one of those "there were three different patches in > as many days to fix the problem, and this is the right one, but maybe > stable should hold off for a while to see that there aren't any > problem reports". > > I don't think there will be any problems from this, but while the > patch is tiny, it's conceptually quite a big change to something that > people haven't really touched for a long time. > > So use your own judgement, but it might be a good idea to wait a week > before backporting this to see if anything screams. I was going to wait a few weeks for this, and the other vt patches that were marked with cc: stable@ before queueing them up. thanks, greg k-h