linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Alex Elder <elder@linaro.org>
Cc: davem@davemloft.net, kuba@kernel.org, bjorn.andersson@linaro.org,
	evgreen@chromium.org, cpratapa@codeaurora.org,
	subashab@codeaurora.org, elder@kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/6] net: ipa: prepare GSI interrupts for runtime PM
Date: Wed, 04 Aug 2021 09:40:07 +0000	[thread overview]
Message-ID: <162807000775.29242.7117719006534625586.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210803140103.1012697-1-elder@linaro.org>

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Tue,  3 Aug 2021 09:00:57 -0500 you wrote:
> The last patch in this series arranges for GSI interrupts to be
> disabled when the IPA hardware is suspended.  This ensures the clock
> is always operational when a GSI interrupt fires.  Leading up to
> that are patches that rearrange the code a bit to allow this to
> be done.
> 
> The first two patches aren't *directly* related.  They remove some
> flag arguments to some GSI suspend/resume related functions, using
> the version field now present in the GSI structure.
> 
> [...]

Here is the summary with links:
  - [net-next,1/6] net: ipa: use gsi->version for channel suspend/resume
    https://git.kernel.org/netdev/net-next/c/decfef0fa6b2
  - [net-next,2/6] net: ipa: move version check for channel suspend/resume
    https://git.kernel.org/netdev/net-next/c/4a4ba483e4a5
  - [net-next,3/6] net: ipa: move some GSI setup functions
    https://git.kernel.org/netdev/net-next/c/a7860a5f898c
  - [net-next,4/6] net: ipa: have gsi_irq_setup() return an error code
    https://git.kernel.org/netdev/net-next/c/1657d8a45823
  - [net-next,5/6] net: ipa: move gsi_irq_init() code into setup
    https://git.kernel.org/netdev/net-next/c/b176f95b5728
  - [net-next,6/6] net: ipa: disable GSI interrupts while suspended
    https://git.kernel.org/netdev/net-next/c/45a42a3c50b5

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-08-04  9:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-03 14:00 [PATCH net-next 0/6] net: ipa: prepare GSI interrupts for runtime PM Alex Elder
2021-08-03 14:00 ` [PATCH net-next 1/6] net: ipa: use gsi->version for channel suspend/resume Alex Elder
2021-08-03 14:00 ` [PATCH net-next 2/6] net: ipa: move version check " Alex Elder
2021-08-03 14:01 ` [PATCH net-next 3/6] net: ipa: move some GSI setup functions Alex Elder
2021-08-03 14:01 ` [PATCH net-next 4/6] net: ipa: have gsi_irq_setup() return an error code Alex Elder
2021-08-03 14:01 ` [PATCH net-next 5/6] net: ipa: move gsi_irq_init() code into setup Alex Elder
2021-08-03 14:01 ` [PATCH net-next 6/6] net: ipa: disable GSI interrupts while suspended Alex Elder
2021-08-04  9:40 ` patchwork-bot+netdevbpf [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=162807000775.29242.7117719006534625586.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=cpratapa@codeaurora.org \
    --cc=davem@davemloft.net \
    --cc=elder@kernel.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;
as well as URLs for NNTP newsgroup(s).