From: Hugh Dickins <hughd@google.com>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Hugh Dickins <hughd@google.com>,
Luca Coelho <luciano.coelho@intel.com>,
Kalle Valo <kvalo@codeaurora.org>,
Mordechay Goodstein <mordechay.goodstein@intel.com>,
Jiri Kosina <jikos@kernel.org>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] iwlwifi: fix DVM build regression in 5.12-rc
Date: Sat, 6 Mar 2021 12:27:09 -0800 (PST) [thread overview]
Message-ID: <alpine.LSU.2.11.2103061224040.1637@eggly.anvils> (raw)
In-Reply-To: <CA+icZUVedsZzJ7qk4fgSZV37M6YUjnP=sfWFK9V9f0y0KpQ4tA@mail.gmail.com>
On Sat, 6 Mar 2021, Sedat Dilek wrote:
> On Sat, Mar 6, 2021 at 8:48 PM Hugh Dickins <hughd@google.com> wrote:
> >
> > There is no iwl_so_trans_cfg if CONFIG_IWLDVM but not CONFIG_IWLMVM:
> > move the CONFIG_IWLMVM guard up before the problematic SnJ workaround
> > to fix the build breakage.
> >
> > Fixes: 930be4e76f26 ("iwlwifi: add support for SnJ with Jf devices")
> > Signed-off-by: Hugh Dickins <hughd@google.com>
>
> See "iwlwifi: pcie: fix iwl_so_trans_cfg link error when CONFIG_IWLMVM
> is disabled" in [1].
>
> - Sedat -
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers.git/commit/?id=62541e266703549550e77fd46138422dbdc881f1
Thanks for looking out that and the other one, Sedat: I swear I checked
linux-next before sending, but my check seems to have been... defective.
Hugh
next prev parent reply other threads:[~2021-03-06 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 19:47 [PATCH 1/2] iwlwifi: fix DVM build regression in 5.12-rc Hugh Dickins
2021-03-06 19:49 ` [PATCH 2/2] iwlwifi: fix DVM boot " Hugh Dickins
2021-03-06 19:53 ` Sedat Dilek
2021-03-06 19:52 ` [PATCH 1/2] iwlwifi: fix DVM build " Sedat Dilek
2021-03-06 20:27 ` Hugh Dickins [this message]
2021-03-06 20:32 ` Sedat Dilek
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=alpine.LSU.2.11.2103061224040.1637@eggly.anvils \
--to=hughd@google.com \
--cc=jikos@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=mordechay.goodstein@intel.com \
--cc=sedat.dilek@gmail.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