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 Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 1A837C25B08 for ; Sat, 13 Aug 2022 07:06:39 +0000 (UTC) Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.95) (envelope-from ) id 1oMlDw-0002kR-9d; Sat, 13 Aug 2022 03:06:20 -0400 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1oMlDs-0002Xg-HK for kernelnewbies@kernelnewbies.org; Sat, 13 Aug 2022 03:06:16 -0400 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id AE3B65C009F; Sat, 13 Aug 2022 03:06:12 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Sat, 13 Aug 2022 03:06:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h=cc :cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm1; t=1660374372; x= 1660460772; bh=BTGcstPul9zJ1b0CFLkAYw/zJ5c/flYyHfwB7Wt9p1Q=; b=F 20Zuxv6gyVnnDVQbiRoKiKd1BW/jJ/63km6+0cFgOomNdrybhB3YJjbaaLhQUgJE XAQgFEwtAHKtxQlefvosa3ryVL+blOFtgsdmZBoKzBQlToQ4tdDnMGbsRVgnEOoJ BJDnNYFZST6onuMQucUXsXeqR76hn1FblwIe+dPSTHoFPxrE4jBEJSRuQLbLSlxu lI3BMtHc6OOvzlPnOmmdrf5VZq+UQ5IMjwHBSt86tLNCErmEQF3b/SzdL8ZijEPP WvhCJJTFeh+MPPUbPmjossh0QItNSjNGtvOpbntjgnpTExRZ3x7xLnKuRzLk7pUr zNtPHvYTZTWKnkK09FiQw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1660374372; x= 1660460772; bh=BTGcstPul9zJ1b0CFLkAYw/zJ5c/flYyHfwB7Wt9p1Q=; b=C Mcrrx5O87hRDlSQ8YJMKvLdiEicfHRFatEFVzFTmI8hpXAiyOyS9P8i0uw47e8/s dNNDqu58ZMrRId0XLRFkCKzL1XQUEXHdci5bKT7shxEOErHA7CooqgCYz0ebrHtk 7o4HTIJnFuk+mxRKyZvkDGrExjTDcX7ZAyp4gD48Wh9kbetUSNoEXtvAAUIEgWgl fmoEj/Lz6Xnr+DdGWuVOsGAHmH8xTFlAjCh7zMjAeNleo/z6ojjmTfcenLC6FXMf zaiCW6Dp1wLHVogBzrK0DL3QsKLCdOZ9TFd2BqsuucWHGbSaGyTf6oLARUM9b6Pj RImLKuUST4abVxovIW0zA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrvdegjedguddujecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvvefukfhfgggtugfgjgesthekredttddtudenucfhrhhomhepifhr vghgucfmjfcuoehgrhgvgheskhhrohgrhhdrtghomheqnecuggftrfgrthhtvghrnheple ehheduudeugeegjefgheeuudffheevueekgfekueefledtjeetieeutdekkeelnecuvehl uhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepghhrvghgsehkrh horghhrdgtohhm X-ME-Proxy: Feedback-ID: i787e41f1:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 13 Aug 2022 03:06:11 -0400 (EDT) Date: Sat, 13 Aug 2022 09:06:09 +0200 From: Greg KH To: Adverg Ebashinskii Subject: Re: How to resubmit patches in the right way after review fixes? Message-ID: References: <86521660342820@mail.yandex.ru> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <86521660342820@mail.yandex.ru> Cc: "kernelnewbies@kernelnewbies.org" X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Errors-To: kernelnewbies-bounces@kernelnewbies.org On Sat, Aug 13, 2022 at 01:39:45AM +0300, Adverg Ebashinskii wrote: > In case I have submitted a patch and some mistakes were pointed what is t= he > right way of submitting a corrected version? > I basically have 2 questions related to patch re-submit. > =A0 > 1. =A0Is it appropriate to submit a new patch starting a new thread or it= 's > required to reply > =A0 =A0 to one of the message in the old patch's thread to preserve a ref= erence to > the old one? New thread is usually fine, but if you want you can do it in the old thread, your choice. > 2. In case the discussion of the patch ended up in patch redesign is it > required to put a version when resubmitting? Yes. > For example the initial patch was [PATCH] sub/sys: summary. Should v2 be = placed > in the description of the new patch like > [PATCH v2] sub/sys: completely different summary due to redesign? Yes. And properly document your changes below the --- line as the documentation asks for. hope this helps, greg k-h _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies