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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 00752C61DA4 for ; Mon, 6 Mar 2023 07:01:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229579AbjCFHBC (ORCPT ); Mon, 6 Mar 2023 02:01:02 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40034 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229457AbjCFHBA (ORCPT ); Mon, 6 Mar 2023 02:01:00 -0500 Received: from msg-4.mailo.com (msg-4.mailo.com [213.182.54.15]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E782F5BA3 for ; Sun, 5 Mar 2023 23:00:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mailo.com; s=mailo; t=1678086047; bh=2uYo5+Ekm6bW81PDMXlh0yBHRTyvtLp33m9m88ampfo=; h=X-EA-Auth:Date:From:To:Cc:Subject:Message-ID:References: MIME-Version:Content-Type:In-Reply-To; b=Pv3/bEP21IMnHDQvGYSyt8QjsopyoTC/7vOVQoa4PChvzBSoQxhD2phiQSmPxTMtA /ZEmxj0BGzEzKxTy+zrYuoc7fwt5qqetwJdmqpEurmb3UqjhzU8UhN7GUIRsa/z8zV MC0WtMuOjSnlWTnknSLbLczmcJ/Jeeb/SpvSN5qo= Received: by b221-2.in.mailobj.net [192.168.90.22] with ESMTP via ip-20.mailobj.net [213.182.54.20] Mon, 6 Mar 2023 08:00:47 +0100 (CET) X-EA-Auth: f8S8VMenhzbwONE81uWdVlU7BSOAyJMGwXGWLrbuklAqboANg0qnzixx2++ggWF+KhOomZvWzU6g9UBqOUX1xAtXZKuV8Wjx Date: Mon, 6 Mar 2023 12:30:35 +0530 From: Deepak R Varma To: Guru Mehar Rachaputi Cc: Greg Kroah-Hartman , Christophe JAILLET , Forest Bond , linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3] staging: vt6655: Macro with braces issue change to inline function Message-ID: References: <3cb45313-209a-8190-12f8-6a2d49e4173b@wanadoo.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 06, 2023 at 06:57:31AM +0100, Guru Mehar Rachaputi wrote: > On Mon, Mar 06, 2023 at 11:06:06AM +0530, Deepak R Varma wrote: > > On Mon, Mar 06, 2023 at 05:52:51AM +0100, Guru Mehar Rachaputi wrote: > > > On Tue, Feb 07, 2023 at 01:49:15PM +0530, Deepak R Varma wrote: > > > > > > Hej Deepak, > > > > > > I have a problem in sending patchset through mutt. > > > I have been trying sending to my own mail address but it won't work. > > > > This could be because of mutt configuration. There are some additional checks if > > you are trying to use mutt with gmail. Search over google or lore old posts to > > know more about it. The important aspect is to configure and test mutt well > > before you use it for sending out patches. > > > > > > > > When sending patchset I think we should use "In-Reply-To" flag and > > > include "Message-ID" to which we want this to be in series to. I tried > > > both "git send-email" feature and mutt "forwarding feature". > > > > I have not used "git send-email", so can't help you there. But mutt has worked > > very well for me. Ensure you are reading and following the instructions from > > this page well: https://kernelnewbies.org/Outreachyfirstpatch > > > > So for example from these patches: 0.patch, 1.patch > how to use "mutt -H" to send patches in one thread? > > if first one is: mutt -H 0.patch > then should second one be: mutt -H 1.patch In-Reply-To: Message-ID? Try this out by sending to yourself and you will know :) There is a section "Using git format-patch to send patchsets" in the link I sent in my last email. Please read that. Deepak. > > > > > > > > Another issue is, how to attach patch file from inside mutt(for example: > > > "mutt -H x.patch" from command line is used to extract header and body of a > > > mail in mutt)? > > > > Why do you want to do that? > > Build a patch file using "git format-patch" and then use "mutt -H" to send the > > patch. Both the commands work directly from the command line. If there is a need > > for any additional attachments in support of your patch [configs, logs, trace as > > evidence, test outcomes etc], you can attach those from within the "mutt -H" > > execution context. > > > > I suggest testing mutt well before you start sending any patches out by sending > > the patches to yourself. Do not use any kernel mailing list for testing. > > > > > > Regards, > > Deepak. > > > > > > > > > > > -- > > > Thanks & Regards, > > > Guru > > > > > > > > > -- > Thanks & Regards, > Guru >