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 C6BAFC00140 for ; Fri, 12 Aug 2022 22:40:15 +0000 (UTC) Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.95) (envelope-from ) id 1oMdJp-0005GY-I9; Fri, 12 Aug 2022 18:39:53 -0400 Received: from forward401j.mail.yandex.net ([2a02:6b8:0:801:2::206]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1oMdJl-0005Fg-KE for kernelnewbies@kernelnewbies.org; Fri, 12 Aug 2022 18:39:49 -0400 Received: from myt6-3780309bcce9.qloud-c.yandex.net (myt6-3780309bcce9.qloud-c.yandex.net [IPv6:2a02:6b8:c12:4020:0:640:3780:309b]) by forward401j.mail.yandex.net (Yandex) with ESMTP id C016D1ACDFF4 for ; Sat, 13 Aug 2022 01:39:45 +0300 (MSK) Received: from 2a02:6b8:c12:3b2d:0:640:29e8:dca3 (2a02:6b8:c12:3b2d:0:640:29e8:dca3 [2a02:6b8:c12:3b2d:0:640:29e8:dca3]) by myt6-3780309bcce9.qloud-c.yandex.net (mxback/Yandex) with HTTP id 5dgLrC0fYCg1-djfaKOGH; Sat, 13 Aug 2022 01:39:45 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1660343985; bh=FfgyToZafM8MViK+gYWatl3NLB/jcL68vnQ0QaHOBcI=; h=Message-Id:Date:Subject:To:From; b=G6Yh/k9WHnfKh0rlteJ86zY07Vurtlq6//TLYP6RCpE/1VaA6A08fbWALWF0bEcl7 3W7OcwplsLLxhRoX92LvZELCqvH92z9pqCv59cEKvCpJs+o09PbupIUugXg59MMDRJ 02NY6zLYF41OPuLUr6drH4ZMUb+pYJVtn053jzBs= Authentication-Results: myt6-3780309bcce9.qloud-c.yandex.net; dkim=pass header.i=@yandex.ru Received: by myt5-29e8dca34993.qloud-c.yandex.net with HTTP; Sat, 13 Aug 2022 01:39:45 +0300 From: Adverg Ebashinskii To: "kernelnewbies@kernelnewbies.org" Subject: How to resubmit patches in the right way after review fixes? MIME-Version: 1.0 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Sat, 13 Aug 2022 01:39:45 +0300 Message-Id: <86521660342820@mail.yandex.ru> 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: multipart/mixed; boundary="===============2670435766234892527==" Errors-To: kernelnewbies-bounces@kernelnewbies.org --===============2670435766234892527== Content-Transfer-Encoding: 8bit Content-Type: text/html; charset=utf-8
In case I have submitted a patch and some mistakes were pointed what is the right way of submitting a corrected version?
I basically have 2 questions related to patch re-submit.
 
1.  Is it appropriate to submit a new patch starting a new thread or it's required to reply
    to one of the message in the old patch's thread to preserve a reference to the old one?
 
2. In case the discussion of the patch ended up in patch redesign is it required to put a version when resubmitting?
 
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?
--===============2670435766234892527== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies --===============2670435766234892527==--