From: David Miller <davem@davemloft.net>
To: elder@linaro.org
Cc: kuba@kernel.org, evgreen@chromium.org, subashab@codeaurora.org,
cpratapa@codeaurora.org, bjorn.andersson@linaro.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/5] net: ipa: endpoint configuration updates
Date: Wed, 01 Jul 2020 15:30:47 -0700 (PDT) [thread overview]
Message-ID: <20200701.153047.1752708672711318364.davem@davemloft.net> (raw)
In-Reply-To: <20200630133304.1331058-1-elder@linaro.org>
From: Alex Elder <elder@linaro.org>
Date: Tue, 30 Jun 2020 08:32:59 -0500
> This series updates code that configures IPA endpoints. The changes
> made mainly affect access to registers that are valid only for RX, or
> only for TX endpoints.
>
> The first three patches avoid writing endpoint registers if they are
> not defined to be valid. The fourth patch slightly modifies the
> parameters for the offset macros used for these endpoint registers,
> to make it explicit when only some endpoints are valid.
>
> The last patch just tweaks one line of code so it uses a convention
> used everywhere else in the driver.
>
> Version 2 of this series eliminates some of the "assert()" comments
> that Jakub inquired about. The ones removed will actually go away
> in an upcoming (not-yet-posted) patch series anyway.
Series applied, thanks.
prev parent reply other threads:[~2020-07-01 22:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 13:32 Alex Elder
2020-06-30 13:33 ` [PATCH net-next v2 1/5] net: ipa: head-of-line block registers are RX only Alex Elder
2020-06-30 13:33 ` [PATCH net-next v2 2/5] net: ipa: metadata_mask register is " Alex Elder
2020-06-30 13:33 ` [PATCH net-next v2 3/5] net: ipa: mode register is TX only Alex Elder
2020-06-30 13:33 ` [PATCH net-next v2 4/5] net: ipa: clarify endpoint register macro constraints Alex Elder
2020-06-30 13:33 ` [PATCH net-next v2 5/5] net: ipa: HOL_BLOCK_EN_FMASK is a 1-bit mask Alex Elder
2020-07-01 22:30 ` David Miller [this message]
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=20200701.153047.1752708672711318364.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bjorn.andersson@linaro.org \
--cc=cpratapa@codeaurora.org \
--cc=elder@linaro.org \
--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
all inboxes | Powered by JetHome®