From: Jakub Kicinski <kuba@kernel.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: m.chetan.kumar@intel.com, Netdev <netdev@vger.kernel.org>,
davem@davemloft.net, johannes@sipsolutions.net,
ryazanov.s.a@gmail.com, loic.poulain@linaro.org,
krishna.c.sudi@intel.com, m.chetan.kumar@linux.intel.com,
linuxwwan@intel.com, Haijun Liu <haijun.liu@mediatek.com>,
Madhusmita Sahu <madhusmita.sahu@intel.com>,
Ricardo Martinez <ricardo.martinez@linux.intel.com>,
Devegowda Chandrashekar <chandrashekar.devegowda@intel.com>
Subject: Re: [PATCH net-next 2/5] net: wwan: t7xx: Infrastructure for early port configuration
Date: Thu, 18 Aug 2022 09:15:27 -0700 [thread overview]
Message-ID: <20220818091527.2b918b36@kernel.org> (raw)
In-Reply-To: <5a74770-94d3-f690-4aa1-59cdbbb29339@linux.intel.com>
Hi Ilpo,
thanks a lot for the reviews. Unfortunately the patches got applied
before your responses - do you have a preference between the MediaTek
following up with fixes or us reverting the v1 completely and
continuing with v2 as if v1 wasn't applied?
next prev parent reply other threads:[~2022-08-18 16:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 4:23 [PATCH net-next 2/5] net: wwan: t7xx: Infrastructure for early port configuration m.chetan.kumar
2022-08-17 12:10 ` Ilpo Järvinen
2022-08-17 15:15 ` Kumar, M Chetan
2022-08-18 10:48 ` Ilpo Järvinen
2022-08-19 9:26 ` Kumar, M Chetan
2022-08-19 22:33 ` Jakub Kicinski
2022-08-17 16:23 ` Kumar, M Chetan
2022-08-18 10:51 ` Ilpo Järvinen
2022-08-18 11:26 ` Kumar, M Chetan
2022-08-18 16:15 ` Jakub Kicinski [this message]
2022-08-30 1:59 ` Sergey Ryazanov
2022-08-31 12:47 ` Kumar, M Chetan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220818091527.2b918b36@kernel.org \
--to=kuba@kernel.org \
--cc=chandrashekar.devegowda@intel.com \
--cc=davem@davemloft.net \
--cc=haijun.liu@mediatek.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=krishna.c.sudi@intel.com \
--cc=linuxwwan@intel.com \
--cc=loic.poulain@linaro.org \
--cc=m.chetan.kumar@intel.com \
--cc=m.chetan.kumar@linux.intel.com \
--cc=madhusmita.sahu@intel.com \
--cc=netdev@vger.kernel.org \
--cc=ricardo.martinez@linux.intel.com \
--cc=ryazanov.s.a@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.