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 7CEFDECAAA1 for ; Wed, 7 Sep 2022 02:43:21 +0000 (UTC) Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.96) (envelope-from ) id 1oVl1o-000443-32; Tue, 06 Sep 2022 22:43:00 -0400 Received: from mail-qk1-x731.google.com ([2607:f8b0:4864:20::731]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1oVl1l-00043k-1Y for kernelnewbies@kernelnewbies.org; Tue, 06 Sep 2022 22:42:57 -0400 Received: by mail-qk1-x731.google.com with SMTP id b9so9616432qka.2 for ; Tue, 06 Sep 2022 19:42:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date; bh=tAMiclrTMwlcurQztCjuUe3mpgHwJVGH+CeDdGDs0sQ=; b=CkNLUytA0CbXlnu5QxTNlbPjKu9w+0iSkrjATdWytD4DGNLFIYnxr4MNFJ6Rq3XHQz CgTY778i7tAbOe1doQvY/JsstnMchBsAGPjcqtvrdzmi7Gl8KC80RrIeIdmjVfe4Hi5n VwJYoyEJP2B530YJV0FBFdQ8VoAcFwobhsgtw6lCMe+RVdnRk1cmd9WgHkJNL5pVqke6 2ICWcMoAwBhEt/nwc35J++FpmUxxQyALB+moDFsWklIkZ3ur0DaCKRw6BR800wT3RCZv E/BMIwjV4IjTF0Ej4SyI6sNsghOsNkF5BAsz7DKcCeYHeABP5UQJ7JoXpI1siNiPz74n 0/sg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date; bh=tAMiclrTMwlcurQztCjuUe3mpgHwJVGH+CeDdGDs0sQ=; b=E0NBZhi2BrmRSy82yr3UU4FmQz3qWqAsiEN8fSAhwjakNdCBUx4HjiHxCCbCMAdnuz LLevzY0bW7meUxVVHb22m+ATszIiFfoCOHInfF2facpPy0IFhGN7HQ5be5loM+VeBTbL hQkib24LkM6y4yGX7xgEK7nxzzeS/Fnpxaa4rgqngB3tbJ8KwPFkWN+w/2vmTtfl72WH gpOLIUGbVvfuHMq27PukLUSfP+T4a5G9FYG6lV463pYokg33uJHXqt8KYiBpbSvuctUF 9+CX/zgsJnCGzt5/b6BevJ5pKwvEgy2SHLXQe0yx8Lm6XvhmLgbUq/4Un+HMLODxl4GP 5u3g== X-Gm-Message-State: ACgBeo2W7hQcq7Ks036wVnsu+Izo9F+L1k4Kjf0gvJw+LkNqEUwI39Q2 Hd6x5v1q6vGBnrAD17DgcZRHj2QhL4eeJ8Ix48yFagBvAfA= X-Google-Smtp-Source: AA6agR6LRbu49RQlCfsiMiM6vqJERCjZ3NSSMbHXL2xme2pbaiA51Yi2yek9E5FaQx5Q8LDN5B2TDyqhNREF7cD/awM= X-Received: by 2002:a05:620a:28d0:b0:6bb:11de:ecbe with SMTP id l16-20020a05620a28d000b006bb11deecbemr1237319qkp.492.1662518575465; Tue, 06 Sep 2022 19:42:55 -0700 (PDT) MIME-Version: 1.0 References: <924111659902451@mail.yandex.ru> In-Reply-To: From: "Sv. Jason M. Christos the First" Date: Tue, 6 Sep 2022 21:42:47 -0500 Message-ID: Subject: Fwd: What is the right thing to do if a patch got ignored? To: 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: multipart/mixed; boundary="===============4839945356805519374==" Errors-To: kernelnewbies-bounces@kernelnewbies.org --===============4839945356805519374== Content-Type: multipart/alternative; boundary="0000000000001f8a1b05e80d450d" --0000000000001f8a1b05e80d450d Content-Type: text/plain; charset="UTF-8" republic ---------- Forwarded message --------- From: Sv. Jason M. Christos the First Date: Mon, Sep 5, 2022, 06:49 Subject: Re: What is the right thing to do if a patch got ignored? To: Adverg Ebashinskii If your John Chevy gets ignored its insubordination you better quit or replace the soldier. On Sun, Aug 7, 2022, 15:07 Adverg Ebashinskii wrote: > 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 > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies@kernelnewbies.org > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > --0000000000001f8a1b05e80d450d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
republic

---------- Forwarded message ---------
From: <= strong class=3D"gmail_sendername" dir=3D"auto">Sv. Jason M. Christos the Fi= rst <thekernelnewbie@gmail.com>
Date: Mon, Sep 5, 2022, 0= 6:49
Subject: Re: What is the right thing to do if a patch got ignored?<= br>To: Adverg Ebashinskii <ebas= hinskii@yandex.ru>


If your John C= hevy gets ignored its insubordination you better quit or replace the soldie= r.

On Sun, Aug 7, 2022, 15:07 Adverg Ebashinskii <ebashinskii@yandex.r= u> wrote:
What is the r= ight things to do if a patch got ignored? Is it appropriate to request a fe= edback by explicitly replying to the thread or ignoring the patch automatic= ally 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.
=C2=A0
Thanks,
= Adverg
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.ke= rnelnewbies.org/mailman/listinfo/kernelnewbies
--0000000000001f8a1b05e80d450d-- --===============4839945356805519374== 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 --===============4839945356805519374==--