[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <dc342ecda69fab39d754c0ba71ae1ca472320611.camel@nvidia.com>
Date: Thu, 13 Jan 2022 19:31:06 +0000
From: Saeed Mahameed <saeedm@...dia.com>
To: "torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...nel.org" <mingo@...nel.org>,
"sfr@...b.auug.org.au" <sfr@...b.auug.org.au>,
"leon@...nel.org" <leon@...nel.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>
Subject: Re: [GIT pull] irq/core for v5.17-rc1
On Thu, 2022-01-13 at 09:01 -0800, Linus Torvalds wrote:
> On Thu, Jan 13, 2022 at 2:13 AM Thomas Gleixner <tglx@...utronix.de>
> wrote:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq-
> > core-2022-01-13
>
> Hmm.
>
> I got a conflict in the mlx driver. It looked trivial, but just to
> make sure I compared against the resolution in linux-next.
>
> My conflict resolution is different, though, and I think mine is the
> correct one (although maybe they end up both being fine).
>
> But I'm just about to leave for travel, and maybe I'm wrong, so I
> just
> wanted to people to verify...
Both will end up the same since mask is NULL.
Bon Voyage!
>
> It's
>
> drivers/net/ethernet/mellanox/mlx5/core/pci_irq.c
>
> and in particular the 'err_xa' release part of mlx5_irq_alloc() - I
> made it use irq_update_affinity_hint() to match the irq_release()
> paths.
>
Agreed, code symmetry is an important standard in mlx5 ! Thanks!.
Powered by blists - more mailing lists