From: Alex Elder <elder@linaro.org>
To: davem@davemloft.net, kuba@kernel.org
Cc: evgreen@chromium.org, subashab@codeaurora.org,
cpratapa@codeaurora.org, bjorn.andersson@linaro.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH net 0/5] net: ipa: endpoint configuration fixes
Date: Wed, 10 Jun 2020 14:53:27 -0500 [thread overview]
Message-ID: <20200610195332.2612233-1-elder@linaro.org> (raw)
This series fixes four bugs in the configuration of IPA endpoints.
See the description of each for more information. The last patch
changes a BUILD_BUG_ON() call into a runtime warning, because
violating the checked condition does not consitute a real bug.
-Alex
Alex Elder (5):
net: ipa: program metadata mask differently
net: ipa: fix modem LAN RX endpoint id
net: ipa: program upper nibbles of sequencer type
net: ipa: header pad field only valid for AP->modem endpoint
net: ipa: warn if gsi_trans structure is too big
drivers/net/ipa/ipa_data-sc7180.c | 2 +-
drivers/net/ipa/ipa_endpoint.c | 97 ++++++++++++++++++-------------
drivers/net/ipa/ipa_main.c | 7 ++-
drivers/net/ipa/ipa_reg.h | 2 +
4 files changed, 65 insertions(+), 43 deletions(-)
--
2.25.1
next reply other threads:[~2020-06-10 19:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 19:53 Alex Elder [this message]
2020-06-10 19:53 ` [PATCH net 1/5] net: ipa: program metadata mask differently Alex Elder
[not found] ` <202006110832.hKzHUsMH%lkp@intel.com>
2020-06-11 19:18 ` Alex Elder
2020-06-10 19:53 ` [PATCH net 2/5] net: ipa: fix modem LAN RX endpoint id Alex Elder
2020-06-10 19:53 ` [PATCH net 3/5] net: ipa: program upper nibbles of sequencer type Alex Elder
2020-06-10 19:53 ` [PATCH net 4/5] net: ipa: header pad field only valid for AP->modem endpoint Alex Elder
2020-06-10 19:53 ` [PATCH net 5/5] net: ipa: warn if gsi_trans structure is too big Alex Elder
2020-06-10 23:36 ` David Miller
2020-06-11 12:58 ` Alex Elder
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=20200610195332.2612233-1-elder@linaro.org \
--to=elder@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=cpratapa@codeaurora.org \
--cc=davem@davemloft.net \
--cc=evgreen@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=subashab@codeaurora.org \
/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).