linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?C=C3=A9dric_Le_Goater_=3Cclg=40kaod=2Eorg=3E?=@ci.codeaurora.org
Cc: netdev@vger.kernel.org, drt@linux.ibm.com, kuba@kernel.org,
	sukadev@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
	davem@davemloft.net
Subject: Re: [PATCH] net/ibmvnic: Cleanup workaround doing an EOI after partition migration
Date: Fri, 18 Feb 2022 11:50:11 +0000	[thread overview]
Message-ID: <164518501164.13243.6810888493004564611.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220218080708.636587-1-clg@kaod.org>

Hello:

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Fri, 18 Feb 2022 09:07:08 +0100 you wrote:
> There were a fair amount of changes to workaround a firmware bug leaving
> a pending interrupt after migration of the ibmvnic device :
> 
> commit 2df5c60e198c ("net/ibmvnic: Ignore H_FUNCTION return from H_EOI
>        		    to tolerate XIVE mode")
> commit 284f87d2f387 ("Revert "net/ibmvnic: Fix EOI when running in
>        		    XIVE mode"")
> commit 11d49ce9f794 ("net/ibmvnic: Fix EOI when running in XIVE mode.")
> commit f23e0643cd0b ("ibmvnic: Clear pending interrupt after device reset")
> 
> [...]

Here is the summary with links:
  - net/ibmvnic: Cleanup workaround doing an EOI after partition migration
    https://git.kernel.org/netdev/net-next/c/7ea0c16a74a4

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



      reply	other threads:[~2022-02-18 11:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18  8:07 [PATCH] net/ibmvnic: Cleanup workaround doing an EOI after partition migration Cédric Le Goater
2022-02-18 11:50 ` 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=164518501164.13243.6810888493004564611.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc==?utf-8?q?C=C3=A9dric_Le_Goater_=3Cclg=40kaod=2Eorg=3E?=@ci.codeaurora.org \
    --cc=davem@davemloft.net \
    --cc=drt@linux.ibm.com \
    --cc=kuba@kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=netdev@vger.kernel.org \
    --cc=sukadev@linux.ibm.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).