From: "Kumar, M Chetan" <m.chetan.kumar@intel.com>
To: Loic Poulain <loic.poulain@linaro.org>,
Johannes Berg <johannes@sipsolutions.net>,
Sergey Ryazanov <ryazanov.s.a@gmail.com>
Cc: Network Development <netdev@vger.kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
David Miller <davem@davemloft.net>,
Dan Williams <dcbw@redhat.com>
Subject: RE: WWAN rtnetlink follow-up
Date: Mon, 7 Jun 2021 15:04:40 +0000 [thread overview]
Message-ID: <5d9c826782d74aefbdf297324362afe7@intel.com> (raw)
In-Reply-To: <CAMZdPi-MrOAfLu6SaxdEqrZyUM=pyq7U8=dokmxdB+6-C3W3aA@mail.gmail.com>
Hi Loic,
I have verified IOSM driver by cherry-picking the below [FIXUP] on top of Johannes & Sergey RFC patch.
Data path is functional. I will resubmit the IOSM Driver patches.
https://git.linaro.org/people/loic.poulain/linux.git/commit/?h=wwan-dev&id=fd7e6d78ebad9930d22e5b5f430cae9ad5fc89fe
https://git.linaro.org/people/loic.poulain/linux.git/commit/?h=wwan-dev&id=6fb7cbd0c0bde0de872744e89ee87e36ed8ec6a7
RFC Series:
https://lore.kernel.org/netdev/20210602082840.85828-1-johannes@xxxxxxxxxxxxxxxx/
https://lore.kernel.org/netdev/20210603044954.8091-1-ryazanov.s.a@gmail.com/
Regards,
M Chetan Kumar
> -----Original Message-----
> From: Loic Poulain <loic.poulain@linaro.org>
> Sent: Friday, June 4, 2021 3:58 PM
> To: Kumar, M Chetan <m.chetan.kumar@intel.com>; Johannes Berg
> <johannes@sipsolutions.net>; Sergey Ryazanov <ryazanov.s.a@gmail.com>
> Cc: Network Development <netdev@vger.kernel.org>; Jakub Kicinski
> <kuba@kernel.org>; David Miller <davem@davemloft.net>; Dan Williams
> <dcbw@redhat.com>
> Subject: WWAN rtnetlink follow-up
>
> Hi folks,
>
> Thanks for your involvement and great work on this WWAN topic. I've picked
> your patches in my tree for testing (with a Qualcomm MHI
> modem):
> https://git.linaro.org/people/loic.poulain/linux.git/log/?h=wwan-dev
>
> This is minimal support for now since mhi_net only supports one link,
> Essentially for testing purposes, but I plan to rework it to support more than
> one once wwan rtnetlink is accepted and merged, This limitation will not
> exist for the Intel IOSM driver.
>
> I'm probably going to rebase that and squash the fix commits (from Sergey
> and I) to Johannes changes if everyone agrees. Then I'll submit the entire
> series.
>
> Not sure what is the procedure for iproute2, should it be included in the
> series or be part of a dedicated one?
>
> Chetan, you can use that tree for your iosm work, or cherry-pick the [FIXUP]
> changes if you already work on the submitted RFC series.
>
> Refs:
> https://lore.kernel.org/netdev/20210602082840.85828-1-
> johannes@xxxxxxxxxxxxxxxx/
> https://lore.kernel.org/netdev/20210603044954.8091-1-
> ryazanov.s.a@gmail.com/
>
> Thanks,
> Loic
next prev parent reply other threads:[~2021-06-07 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 10:27 WWAN rtnetlink follow-up Loic Poulain
2021-06-07 15:04 ` Kumar, M Chetan [this message]
2021-06-08 9:18 ` Kumar, M Chetan
2021-06-08 9:43 ` Loic Poulain
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=5d9c826782d74aefbdf297324362afe7@intel.com \
--to=m.chetan.kumar@intel.com \
--cc=davem@davemloft.net \
--cc=dcbw@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=loic.poulain@linaro.org \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).