From: Jakub Kicinski <kuba@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Kalle Valo <kvalo@kernel.org>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Gregory Greenman <gregory.greenman@intel.com>,
Luca Coelho <luciano.coelho@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: mainline build failure due to c1918196427b ("iwlwifi: pcie: simplify MSI-X cause mapping")
Date: Fri, 27 May 2022 17:24:29 -0700 [thread overview]
Message-ID: <20220527172429.6cd3110e@kernel.org> (raw)
In-Reply-To: <604ee91b52c79c575bb0ac0849f504be354bf404.camel@sipsolutions.net>
On Fri, 27 May 2022 11:23:10 +0200 Johannes Berg wrote:
> On Fri, 2022-05-27 at 12:20 +0300, Kalle Valo wrote:
> >
> > iwlwifi: pcie: rename CAUSE macro
> >
> > https://patchwork.kernel.org/project/linux-wireless/patch/20220523220300.682be2029361.I283200b18da589a975a284073dca8ed001ee107a@changeid/
> >
> > It's marked as accepted but I don't know where it's applied to, Gregory?
>
> Gregory picked it up to our internal tree.
>
> > This is failing the build, should Linus apply the fix directly to his
> > tree?
>
> I had previous asked Jakub if he wanted to do that, but he didn't (yet).
> I don't know what's the best course of action right now...
>
> No objections to it taking any kind of fast path though :)
IIRC this is a warning and it's on MIPS only [1], so if it can make its
way to your Wed PR and I'll send it to Linus on Thu - that should be
good enough (I think).
[1] https://lore.kernel.org/all/20220523125906.20d60f1d@kernel.org/
prev parent reply other threads:[~2022-05-28 0:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 9:13 mainline build failure due to c1918196427b ("iwlwifi: pcie: simplify MSI-X cause mapping") Sudip Mukherjee
2022-05-27 9:20 ` Kalle Valo
2022-05-27 9:23 ` Johannes Berg
2022-05-28 0:24 ` Jakub Kicinski [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=20220527172429.6cd3110e@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=gregory.greenman@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.