From: Kalle Valo <kvalo@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>, Luca Coelho <luciano.coelho@intel.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: pull-request: wireless-next-2022-03-11
Date: Mon, 14 Mar 2022 20:20:13 +0200 [thread overview]
Message-ID: <87wngwwg4i.fsf@tynnyri.adurom.net> (raw)
In-Reply-To: <20220311130530.70d9faa6@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (Jakub Kicinski's message of "Fri, 11 Mar 2022 13:05:30 -0800")
Jakub Kicinski <kuba@kernel.org> writes:
> On Fri, 11 Mar 2022 13:40:28 +0100 Johannes Berg wrote:
>> Hi,
>>
>> Here's another (almost certainly final for 5.8) set of
>> patches for net-next.
>
> 5.18 ;)
>
>> Note that there's a minor merge conflict - Stephen already
>> noticed it and resolved it here:
>> https://lore.kernel.org/linux-wireless/20220217110903.7f58acae@canb.auug.org.au/
>>
>> I didn't resolve it explicitly by merging back since it's
>> such a simple conflict, but let me know if you want me to
>> do that (now or in the future).
>
> Looks like commit e8e10a37c51c ("iwlwifi: acpi: move ppag code from mvm
> to fw/acpi") uses spaces for indentation?
Luca, can you check that, please?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-03-14 18:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 12:40 pull-request: wireless-next-2022-03-11 Johannes Berg
2022-03-11 21:05 ` Jakub Kicinski
2022-03-14 18:20 ` Kalle Valo [this message]
2022-03-11 21:20 ` patchwork-bot+netdevbpf
2022-03-12 1:06 ` Jakub Kicinski
2022-03-12 1:08 ` Jakub Kicinski
2022-03-14 18:21 ` Kalle Valo
2022-03-14 18:37 ` Jakub Kicinski
2022-03-14 20:17 ` Johannes Berg
2022-03-14 20:41 ` Jakub Kicinski
2022-03-14 20:45 ` Johannes Berg
2022-03-14 20:51 ` Jakub Kicinski
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=87wngwwg4i.fsf@tynnyri.adurom.net \
--to=kvalo@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=netdev@vger.kernel.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