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 E0DB2C6FD1D for ; Mon, 20 Mar 2023 10:15:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229970AbjCTKPC (ORCPT ); Mon, 20 Mar 2023 06:15:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52608 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229648AbjCTKO7 (ORCPT ); Mon, 20 Mar 2023 06:14:59 -0400 Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 60CB4C679 for ; Mon, 20 Mar 2023 03:14:58 -0700 (PDT) Received: by mail-ed1-x52c.google.com with SMTP id eg48so44369038edb.13 for ; Mon, 20 Mar 2023 03:14:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1679307297; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=HvoaCsxD8j+MlDGCUL2UcBhM2jG+i14Rfbl7/FhMycg=; b=FGb8HHAG4Qm7kRI4qls4jY8N7C0C3sZoNOglCJSYipb2PSMj0u5OmqG0XkuwtkDTPj HsYq9S5eyOAp5gfinLuagefvgsF+M5bKbstRIeSUPryos57DD2b1FItRrRkEzbkeWlia UBMoBKr2hAo/PoTmaJ+42Iex9PVKGwSmU88IbvpTz4TRk4ozmNPgLvufiF2PSOl3gxJE Wvh8kmTukLMkTgxeoqtk6My/+wmJIaXioPxeLKmPqc7DQM8RgWaJXrkEvm2n/EjoK5Qv ey9FdKDove8Mc6WHwEMWmtIcbcL5UbKlUagRhxLcGuzQbEVXLqRMXZXsH+QVSJCNLelD wFIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679307297; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=HvoaCsxD8j+MlDGCUL2UcBhM2jG+i14Rfbl7/FhMycg=; b=BGLw+8u912mI0uH2FS/o/UGsBRYLxYzuTnqaF1U+Wuq3Yz/Xm1Ue7KMXXHMpNbDcYY uhJ7tOk+2q4V2EihVPg9eDbNgpHrQt7ijBWefUs4FAbMHZIDcz7hEyRPfqyjgknKCMdn hIcRuf4kIJLOa5OxePdLzggEf1+sP85KbJhgoKQgJNjg/SotLyLtAlqB/SX3/7LLP8/Z N/3CMqXweymLXM7gzVfEI99Ls4wIc008gP/ZOn8QEuSzkeisNMSLnupI9kjRk4sCKpuk AkVWMezE5jGZJRIRNpdMzTWaaAbz2axRIPiDe8cSUBGYcRvP8DDFz3dER4JoG98LevJh K8DQ== X-Gm-Message-State: AO0yUKXxgQTRa7F93i5KOcTXzZBFQr0ijwY2Dk/1CIRPNtQycvUzj11U vNHtdDZ7Sq72HxONDsI0uOQ= X-Google-Smtp-Source: AK7set+TM0hC3s6i6HZiMrQ7bJN49IFKhhZ+d/Yhr4dJenpButGzu2Z8VUe+Szsa7sAlNsUVWBjyEw== X-Received: by 2002:a17:906:51d0:b0:885:a62c:5a5c with SMTP id v16-20020a17090651d000b00885a62c5a5cmr9709042ejk.46.1679307296787; Mon, 20 Mar 2023 03:14:56 -0700 (PDT) Received: from [192.168.1.16] ([41.42.177.251]) by smtp.gmail.com with ESMTPSA id z1-20020a1709064e0100b00931baabe36csm4150848eju.63.2023.03.20.03.14.55 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 20 Mar 2023 03:14:56 -0700 (PDT) Message-ID: <3c9e2fd0-fec8-2aa7-0e68-601b13cc86dd@gmail.com> Date: Mon, 20 Mar 2023 12:14:54 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [PATCH] staging: greybus: use inline function for macros To: Julia Lawall Cc: gregkh@linuxfoundation.org, outreachy@lists.linux.dev, johan@kernel.org, elder@kernel.org, linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev References: <20230319201324.253874-1-eng.mennamahmoud.mm@gmail.com> <0f02a3ff-801b-1e1f-5c03-009a05708709@gmail.com> <402ffcbe-bb29-7035-68f4-2741532a6d67@gmail.com> <649afe06-e069-e046-21ec-0d86243a4bfa@gmail.com> <8e9724a0-226d-eb81-69c3-d59889e37e1f@gmail.com> Content-Language: en-US From: Menna Mahmoud In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On ٢٠‏/٣‏/٢٠٢٣ ٠٨:٠٠, Julia Lawall wrote: >>>> and version that I have submitted, should I do anything about it as you >>>> said >>>> it is wrong solution? >>> My concern was the blank line after each of the structure definitions, >>> which is not in Greg's tree, so he can't apply the patch. Other than >>> that, if the code compiles it is at least going in the right direction. >>> >>> Please fix the newlines issue, and then send the patch again. >>> >>> julia >> >> Okay I will fix it, but will send it as a new patch not v3, right? > Why as a new patch? The change is the same as in v2, and sending v3 makes > it clear that v2 should be ignored. > > julia Okay, thanks. Menna