Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp756264pxj; Wed, 16 Jun 2021 12:52:16 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz5E4UqGBw0HXEz4giTS4p7j19R2o7vy9Wr6C6s2DC8idwH08oRJou3zvMnTjb0sRHLpnk+ X-Received: by 2002:a02:3506:: with SMTP id k6mr959716jaa.39.1623873136167; Wed, 16 Jun 2021 12:52:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623873136; cv=none; d=google.com; s=arc-20160816; b=rdN+vBq9elLB6Hdhhaw/UZCAyECajXpRB3IgbUYZ+4qgrd6sevWqK5KT+iUlWc68ai 2oeD6mEYlsXhkKIckV1l2A3ZEnLUq7IuL+aUsBqSvGNWr2rmn29DSztn7AtpG3xg5sTj teOQyYd61rjiAzxFLIZd0K60ipDXQONoK0W2JY0KWo2SeXGvAtQNLvL0bhywGjg0b1rQ 2HUaa8QJ1LP/UloNDSpSU/CCEBUN4Z3otKfhAIr7dDTYb4g+IMTtcMj11Q8wTW9FVU9+ LCcb83ARL8QjGlqfghEnj+ZvS8jqNv5HxNHVLciBSUnNFHuQqtgvIokGar8WTI8X9Rqt pKcg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=RpA6AhJsyaxTLCvUFDmL9/WHFTtTyMU2s74FPxy23zw=; b=vnkqz7r+xPUV74X7rV7QCzkZIT809QbKp11AIsvrV+DwpsB+cEzDvrPcllTyJ0LkhT Qoh/qbrriWAK0QSj1xFK9yj9I1T8bK+5UagZ89VXrk+3ZhlBdc04sgJPx8u7QFNs1t+t NfsNAomRbnX+7/h/br8wrmPGkUFoMUGnQ38l1h9WuQ6u6dZFlgAc0smSQzQTtuD/gd37 oti0Io7X5N3Xfp0B6JQ5pohhHckni+a086sWfT8MDHpAySlqieX7/GU/OmqbpoPAcqUP m9Z+UZ3NHzUSaYvmjF7SDWZ3qjoGDpCl11XEj6d8s2+9IxRYcHu613ltrJuklLdVWYfT rXSQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w2si3130935iop.49.2021.06.16.12.52.03; Wed, 16 Jun 2021 12:52:16 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233532AbhFPNpf (ORCPT + 99 others); Wed, 16 Jun 2021 09:45:35 -0400 Received: from mail.kernel.org ([198.145.29.99]:43528 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233544AbhFPNpa (ORCPT ); Wed, 16 Jun 2021 09:45:30 -0400 Received: from gandalf.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (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 67D2E611EE; Wed, 16 Jun 2021 13:43:23 +0000 (UTC) Date: Wed, 16 Jun 2021 09:43:21 -0400 From: Steven Rostedt To: Olivier Langlois Cc: Jens Axboe , Pavel Begunkov , Ingo Molnar , io-uring@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 2/3] io_uring: minor clean up in trace events definition Message-ID: <20210616094321.671b82dc@gandalf.local.home> In-Reply-To: References: <60be7e31.1c69fb81.a8bfb.2e54SMTPIN_ADDED_MISSING@mx.google.com> <2752dcc1-9e56-ba31-54ea-d2363ecb6c93@gmail.com> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 16 Jun 2021 09:33:18 -0400 Olivier Langlois wrote: > I do not get any errors but I have noticed too that my emails weren't > accepted by the lists. > > They will accept replies in already existing threads but they won't let > me create new ones. ie: accepting my patches. How are you sending your patches? The patches that were rejected, did not have the "Message-ID:" tag in the header. If you look at my email (and yours that I'm replying to now) you'll see something like this: Message-ID: (that's from the email I'm replying to). All emails are suppose to have this tag. This is what is used to map replies in a way that your email client can see what email is replying to which email. Again, from your email: In-Reply-To: That's because the email you replied to had: Message-ID: This is also used for mail archives, as message ids are used to differentiate emails from each other. But if the Message-ID is missing, the archives have no idea to map it. I'm guessing that the mailing lists also flag any email that is missing a Message-ID as spam. Thus, you should find out what is wrong with your client software that is sending out the patches, and see why it's not including the Message-ID. -- Steve