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 A244EC19F2A for ; Sun, 7 Aug 2022 20:07:51 +0000 (UTC) Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.95) (envelope-from ) id 1oKmYw-0005us-FX for kernelnewbies@archiver.kernel.org; Sun, 07 Aug 2022 16:07:50 -0400 Received: from forward401o.mail.yandex.net ([37.140.190.194]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1oKmWt-0003BC-F1 for kernelnewbies@kernelnewbies.org; Sun, 07 Aug 2022 16:05:43 -0400 Received: from vla1-5340769fcd0e.qloud-c.yandex.net (vla1-5340769fcd0e.qloud-c.yandex.net [IPv6:2a02:6b8:c0d:d1d:0:640:5340:769f]) by forward401o.mail.yandex.net (Yandex) with ESMTP id E1978132CD15 for ; Sun, 7 Aug 2022 23:05:39 +0300 (MSK) Received: from 2a02:6b8:c0d:1a00:0:640:58d:120a (2a02:6b8:c0d:1a00:0:640:58d:120a [2a02:6b8:c0d:1a00:0:640:58d:120a]) by vla1-5340769fcd0e.qloud-c.yandex.net (mxback/Yandex) with HTTP id N5ZVebAgmOs1-5dgKEWtc; Sun, 07 Aug 2022 23:05:39 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1659902739; bh=9pSoERg+BoDbRI7JUSvWDU6LffNwyv7WOox4vVQH5fs=; h=Message-Id:Date:Subject:To:From; b=oyIfyuIx0cw9uCfLU8foSwwEe7yuDdgdCUUK9ksLIVQe22dGYkYilvkWyxbmXmP8U PhvHa9nKgCKx9hK/5Q69EBqTDyp9kN3r7VYaq+D+Evyt2c09zln8hxEP4QcbWRFak6 i2YSb+e0fZvod9JLfvBsWwRYa67EUztZeTJELIJg= Authentication-Results: vla1-5340769fcd0e.qloud-c.yandex.net; dkim=pass header.i=@yandex.ru Received: by vla1-058d120ab76c.qloud-c.yandex.net with HTTP; Sun, 07 Aug 2022 23:05:39 +0300 From: Adverg Ebashinskii To: "kernelnewbies@kernelnewbies.org" Subject: What is the right thing to do if a patch got ignored? MIME-Version: 1.0 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Sun, 07 Aug 2022 23:05:39 +0300 Message-Id: <924111659902451@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="===============7247972711884804767==" Errors-To: kernelnewbies-bounces+kernelnewbies=archiver.kernel.org@kernelnewbies.org --===============7247972711884804767== Content-Transfer-Encoding: 8bit Content-Type: text/html; charset=utf-8
What is the right things to do if a patch got ignored? Is it appropriate to request a feedback by explicitly replying to the thread or ignoring the patch automatically means that it was rejected? If it's possible to request a feedback how long should I before doing that? I'd like to request a feedback to understand what was wrong about the patch to not do the same mistake when submitting a patch next time.
 
Thanks,
Adverg
--===============7247972711884804767== 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 --===============7247972711884804767==--