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 D9B23C742A7 for ; Mon, 6 Mar 2023 16:05:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231454AbjCFQFT (ORCPT ); Mon, 6 Mar 2023 11:05:19 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42136 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231406AbjCFQA4 (ORCPT ); Mon, 6 Mar 2023 11:00:56 -0500 Received: from mail-oi1-x231.google.com (mail-oi1-x231.google.com [IPv6:2607:f8b0:4864:20::231]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CB83C2ED79 for ; Mon, 6 Mar 2023 08:00:51 -0800 (PST) Received: by mail-oi1-x231.google.com with SMTP id bh20so7384491oib.9 for ; Mon, 06 Mar 2023 08:00:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1678118451; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=6w5BS2JYz2kZQkEeuywTfHp8NdeDU1CPaV3Ohjlv1m8=; b=jO/l6gl5WIN4qll5tf9EjB45mGMXbF463tOH89tGjxuVT8rN5LVChRIjnmUBkSumvb RrtRzOV6kjh0MXFsdfmH50kurJ2Kcfvf1d3cks8Za+NkHteZ12/b2yR3MKI7CfcrUCl9 bnwq92HMES5s2kKG8McF6/oLzlevGX92itc6m/D8Xvra2G+xropwYFBKv8mCN1sOb4Sf pG/q58DLxiSS2Sa+srZHTss/oXTz/lTXOOk3ND8by2e6or+fU5VysnvlAJNhem4h9VyM G0FWxbT6tbW78cV7yRfcn6dpxqNtlqPzzw0Nmh7dIx83u2oB3gbgunF3xtEjMhgZm+cZ gCWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678118451; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=6w5BS2JYz2kZQkEeuywTfHp8NdeDU1CPaV3Ohjlv1m8=; b=tFrWWwsTpVz5UQSw76OTZPThouTcQ7gU1kW4ggYxH2pJ/EFlohOjpNAiqyJA+P3sop hC+P9/xSvwjz9xCxOjYTVv2pxhS44X2eaDjoNWXbdYkJZYheD2zMHSUuRvM7epR2w/yI mORCY32Aou1azNVoqHsIhICMsdKArv5Dor6Kse/GHUvP7z8+kciEPeLmI5UlzwlAfSPw qcyxrxz/CoxcTtmCHlNMKk3z0tAgFLASjJnAF+CWcpgKxj+oPUsxkxdS7/ckmDGQ2dy8 FeUdhksnOALDIQwN2zE9848kQbOElY3kDmN87ISoIoex5oyJmZ4E+k5s9KmykaWJXHxn UTdw== X-Gm-Message-State: AO0yUKVKx3RqjywZM/+U9kHDbUfeGLwZCBXWpyaRx4A7RnKTdX2RrUQ2 BrF5txKq63cCob5bpVvWS6oyIR/gCS3XG+8kc5zQ/w== X-Google-Smtp-Source: AK7set/8Jpy/ZNN0pALMDvlhUPzgIohhx0Xl1N5UUOt7NLlnLvVlmpPrWQ1oiOW7cEbO8NieW/hXh1TkDnHVteaOCRs= X-Received: by 2002:a54:4612:0:b0:383:fad3:d19 with SMTP id p18-20020a544612000000b00383fad30d19mr3566227oip.9.1678118450998; Mon, 06 Mar 2023 08:00:50 -0800 (PST) MIME-Version: 1.0 References: <20221124074725.74325-1-haozhe.chang@mediatek.com> <54c37c8f8eb7f35e4bb983b9104bd232758bae7b.camel@mediatek.com> In-Reply-To: From: Loic Poulain Date: Mon, 6 Mar 2023 17:00:14 +0100 Message-ID: Subject: Re: [PATCH v5] wwan: core: Support slicing in port TX flow of WWAN subsystem To: =?UTF-8?B?SGFvemhlIENoYW5nICjluLjmtanlk7Ip?= Cc: "stephan@gerhold.net" , "oneukum@suse.com" , "linux-kernel@vger.kernel.org" , "linux-usb@vger.kernel.org" , "linux-remoteproc@vger.kernel.org" , "linuxwwan@intel.com" , "m.chetan.kumar@intel.com" , "linux-mediatek@lists.infradead.org" , =?UTF-8?B?SHVhIFlhbmcgKOadqOWNjik=?= , "chiranjeevi.rapolu@linux.intel.com" , =?UTF-8?B?SGFpanVuIExpdSAo5YiY5rW35YabKQ==?= , "linux-arm-kernel@lists.infradead.org" , "ryazanov.s.a@gmail.com" , "kuba@kernel.org" , =?UTF-8?B?WGlheXUgWmhhbmcgKOW8oOWkj+Wuhyk=?= , "pabeni@redhat.com" , "edumazet@google.com" , "chandrashekar.devegowda@intel.com" , "johannes@sipsolutions.net" , "gregkh@linuxfoundation.org" , "shangxiaojing@huawei.com" , =?UTF-8?B?TGFtYmVydCBXYW5nICjnjovkvJ8p?= , "matthias.bgg@gmail.com" , "davem@davemloft.net" , "ricardo.martinez@linux.intel.com" , "netdev@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Haozhe, On Fri, 3 Mar 2023 at 09:59, Haozhe Chang (=E5=B8=B8=E6=B5=A9=E5=93=B2) wrote: > I'm sorry to bother you, but I want to know whether my patch is accepted = by the community. > Because it seems to be a merge window, but the patch state still is "Not = Applicable". Could you > give me some suggestions about this patch state? Please rebase your change and resubmit the latest version (can add RESEND tag to subject). Please, also read my previous reply, I mentioned your change should target net-next... you should add it in the subject (look at the documentation or other mailing-list patches). Regards, Loic