Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp956871imu; Wed, 16 Jan 2019 10:14:08 -0800 (PST) X-Google-Smtp-Source: ALg8bN6PZGxqNx9iKjwXZx11bPZRxfEbV6nBwrdO3OzgzMi7u3lmawwRoFro46Tlqno7iV/mLs0w X-Received: by 2002:a63:6006:: with SMTP id u6mr10165455pgb.176.1547662448315; Wed, 16 Jan 2019 10:14:08 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547662448; cv=none; d=google.com; s=arc-20160816; b=bxeVp0HEqaF/akfu7x2Y+ZevjDWLlflAewzvAMBY2ztXaNDJxk6P+r86KeWI17pDf1 LgAP3in+jR6za8YphTJiRrZ5AGGVmwhGEWi2px8c+JPxndH+IN/ByF7MLwuC5rdn+GPf OMY7BJCHPRk7nTwB6/U0S7ix0OALewEra9k5posBqDfS6c+GvUDNlg7la4osAD3tP6C1 n53eVk6B4ehksd+hLUIgLaIQDeQ8Ah7lRTvp8ix/R4G494VkZY3Wg6+cTc1Q79YZhqRB A0HGLyfWz/B9sbUUsvM8U2wSs1giiisWoZZ+nNUDm0OP07sOHskzQeV9W3oTpi/5P5LB 8Bgw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=8SquyAY8s1hcPMSMRPHkq4r44tsfoSinDyKioMKGzYo=; b=pi1Qq7Ps5r8uIaJsFJYrZ3tWvGA/6WUmTAhc3Kt5xQSQS5p9famgo9Cy1iYE3+gcx8 6uV1MLiWCXLpW4rXPHipHEODzlUQqtYV0dJmotkTGIrTCyHHaS2rLKHnmQC0q/vNTVX5 bgStpHsghKoG4hmiFGRhs7nKLi4BjOyIa8TyqUbg008tJeeve0WmJRmyJGmB5LyEIdqw jrjZoA/C8bzAqDPZ/mjERfXUR+aMACqYfjyT2bBNKg4To2GlZJ5PW/VH0g4ASLaTxIHq E2hY0e0NHs/yBP8a0HzVYskSL+44dO2H6i7h3y6gpBEhy98rANMzKSLXWMUvgUEWFYUm ux3g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=JXbh9sMy; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 91si6862278ply.222.2019.01.16.10.13.40; Wed, 16 Jan 2019 10:14:08 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=JXbh9sMy; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387836AbfAPGhR (ORCPT + 99 others); Wed, 16 Jan 2019 01:37:17 -0500 Received: from mail.kernel.org ([198.145.29.99]:58054 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730938AbfAPGhR (ORCPT ); Wed, 16 Jan 2019 01:37:17 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id E54CC20840; Wed, 16 Jan 2019 06:37:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1547620636; bh=8UotO4s9VENwI57eiv8B6JGyML7bIU6RQFM8MEfhBm8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=JXbh9sMywI8JzHFIac27OU9h4BbsotQ8hX+d40WpTtMJ8UttQVlskYdOanTPceZ8R Ua/ykTszXa0tlBdf7jGgYPo3Ai9gxAxHe0+uXpog8bXo5jcmLMSYb+M9bkxwjNjLj2 rI9CuXvgdJ54Ltr8tBFwzKsPosHncUBDK50KX8cc= Date: Wed, 16 Jan 2019 07:37:14 +0100 From: Greg Kroah-Hartman To: Pavel Shilovskiy Cc: "linux-kernel@vger.kernel.org" , "stable@vger.kernel.org" , Jeff Layton , Steven French Subject: Re: [PATCH 4.20 14/57] CIFS: Do not hide EINTR after sending network packets Message-ID: <20190116063714.GA24920@kroah.com> References: <20190115154910.734892368@linuxfoundation.org> <20190115154911.514830122@linuxfoundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.2 (2019-01-07) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 15, 2019 at 07:22:38PM +0000, Pavel Shilovskiy wrote: > Hi Greg, > > I am wondering if it is possible to include exact stable kernel > version (e.g. 4.20.3 in this case) in the email. This would help to > quickly understand which kernel version should be installed in order > to get the fix. Given that this is not in a released kernel yet, it's hard to give you a final version :) We have had times when a stable release happens while a -rc is out for review due to special circumstances, so you couldn't always rely on my email for this, as well as the fact that sometimes we drop patches from -rc releases before they are in a real release, so such an email would lie and confuse people. Just watch the kernel releases, and use git to see what commit is in what release, it's not that difficult. Especially as you are going to want to track this across multiple stable releases, so any guess I might provide here isn't going to help you out much. greg k-h