From: Dmitry Osipenko <digetx@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Arend van Spriel <aspriel@gmail.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Chi-hsien Lin <chi-hsien.lin@infineon.com>,
Wright Feng <wright.feng@infineon.com>,
Chung-hsien Hsu <chung-hsien.hsu@infineon.com>,
Kalle Valo <kvalo@codeaurora.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Stefan Hansson <newbyte@disroot.org>,
Arend van Spriel <arend.vanspriel@broadcom.com>
Subject: Re: [PATCH v3] brcmfmac: firmware: Fix firmware loading
Date: Sun, 8 Aug 2021 17:23:03 +0300 [thread overview]
Message-ID: <018613ac-d479-46e4-5654-9b8ee56e3937@gmail.com> (raw)
In-Reply-To: <CACRpkdZs4Zw5k6Hv0-PDKtrqXpEhTDn9OjwDJDvwJvsXJWDUvQ@mail.gmail.com>
08.08.2021 02:02, Linus Walleij пишет:
> On Thu, Aug 5, 2021 at 12:31 PM Dmitry Osipenko <digetx@gmail.com> wrote:
>
>> Combining my previous comments together, I rewrote it like this:
>
> I like this, can you fold in your patch on top of mine, add your
> Signed-off-by at the end and resend to the list?
>
> That way we get a clean record of the delivery path and also the
> patch looks like you want it :)
>
> You can perhaps tag on v4 on the [PATCH] as well so it's clear
> for Kalle to apply this version. (Hoping Arnd will be fine with it as
> well.)
Alright, let's try that.
next prev parent reply other threads:[~2021-08-08 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 9:30 [PATCH v3] brcmfmac: firmware: Fix firmware loading Linus Walleij
2021-08-05 10:31 ` Dmitry Osipenko
2021-08-07 23:02 ` Linus Walleij
2021-08-08 14:23 ` Dmitry Osipenko [this message]
2021-08-05 11:35 ` Arend van Spriel
2021-08-06 15:45 ` Dmitry Osipenko
2021-08-06 16:00 ` Dmitry Osipenko
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=018613ac-d479-46e4-5654-9b8ee56e3937@gmail.com \
--to=digetx@gmail.com \
--cc=arend.vanspriel@broadcom.com \
--cc=aspriel@gmail.com \
--cc=chi-hsien.lin@infineon.com \
--cc=chung-hsien.hsu@infineon.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=kvalo@codeaurora.org \
--cc=linus.walleij@linaro.org \
--cc=linux-wireless@vger.kernel.org \
--cc=newbyte@disroot.org \
--cc=wright.feng@infineon.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