From: Kalle Valo <kvalo@codeaurora.org>
To: Felix Fietkau <nbd@nbd.name>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: pull request: mt76 2021-10-23
Date: Wed, 27 Oct 2021 12:32:20 +0300 [thread overview]
Message-ID: <87bl3a7qzf.fsf@codeaurora.org> (raw)
In-Reply-To: <6d896d65-235c-41b8-89bd-8349f031dd53@nbd.name> (Felix Fietkau's message of "Sat, 23 Oct 2021 13:28:09 +0200")
Felix Fietkau <nbd@nbd.name> writes:
> Hi Kalle,
>
> here's a pull request with some follow-up fixes for 5.16
>
> - Felix
>
> The following changes since commit 753453afacc0243bd45de45e34218a8d17493e8f:
>
> mt76: mt7615: mt7622: fix ibss and meshpoint (2021-10-23 10:29:39 +0300)
>
> are available in the Git repository at:
>
> https://github.com/nbd168/wireless tags/mt76-for-kvalo-2021-10-23
>
> for you to fetch changes up to 52a99a13cb880845cd77f1da7136d689347489ef:
>
> mt76: connac: fix unresolved symbols when CONFIG_PM is unset (2021-10-23 13:23:45 +0200)
>
> ----------------------------------------------------------------
> mt76 patches for 5.16
>
> * fix a compile error with !CONFIG_PM
> * cleanups
> * MT7915 DBDC fixes
> * endian warning fixes
Unfortunately I had already applied some of the fixes directly:
753453afacc0 mt76: mt7615: mt7622: fix ibss and meshpoint
a88cae727b3e mt76: mt7921: fix Wformat build warning
8603caaec98f mt76: mt7921: fix mt7921s Kconfig
Fortunately git-pull seems to handle this without problems so my plan is
to pull this anyway, despite the the duplicate commits. But if you
prefer to instead rebase your tree and send a new pull request, do let
me know. Either way is fine for me.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-10-27 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 11:28 pull request: mt76 2021-10-23 Felix Fietkau
2021-10-27 9:32 ` Kalle Valo [this message]
2021-10-27 15:37 ` Kalle Valo
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=87bl3a7qzf.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
/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).