From: Kalle Valo <kvalo@qca.qualcomm.com>
To: David Miller <davem@davemloft.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: pull-request: wireless-drivers-next 2017-07-28
Date: Fri, 28 Jul 2017 14:05:59 +0000 [thread overview]
Message-ID: <87d18kvepm.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <87h8xwvevj.fsf@kamboji.qca.qualcomm.com> (Kalle Valo's message of "Fri, 28 Jul 2017 17:02:24 +0300")
Kalle Valo <kvalo@codeaurora.org> writes:
> Hi Dave,
>
> here's a pull request for net, more info the signed tag below. Please
> let me know if there are any problems.
>
> Kalle
>
> The following changes since commit d755cbc26e8295ae8e5d30425364e093b4247a=
85:
>
> Merge tag 'iwlwifi-for-kalle-2017-07-21' of git://git.kernel.org/pub/sc=
m/linux/kernel/git/iwlwifi/iwlwifi-fixes (2017-07-21 14:33:27 +0300)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers.gi=
t tags/wireless-drivers-for-davem-2017-07-28
Argh, the subject is of course wrong and it should be:
pull-request: wireless-drivers 2017-07-28
So this pull request is for net tree to get these two brcmfmac fixes to
4.13. Otherwise the pull request is correct so I don't submit a new one
(but let me know if you prefer that).
--=20
Kalle Valo=
next prev parent reply other threads:[~2017-07-28 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 14:02 pull-request: wireless-drivers-next 2017-07-28 Kalle Valo
2017-07-28 14:05 ` Kalle Valo [this message]
2017-07-29 22:30 ` David Miller
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=87d18kvepm.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).