From: David Miller <davem@davemloft.net>
To: kvalo@qca.qualcomm.com
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: pull-request: wireless-drivers-next 2017-07-28
Date: Sat, 29 Jul 2017 15:30:42 -0700 (PDT) [thread overview]
Message-ID: <20170729.153042.505134537790079396.davem@davemloft.net> (raw)
In-Reply-To: <87d18kvepm.fsf@kamboji.qca.qualcomm.com>
From: Kalle Valo <kvalo@qca.qualcomm.com>
Date: Fri, 28 Jul 2017 14:05:59 +0000
> 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 d755cbc26e8295ae8e5d30425364e093b4247a85:
>>
>> Merge tag 'iwlwifi-for-kalle-2017-07-21' of git://git.kernel.org/pub/scm/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.git 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
Yeah that makes more sense. :)
> 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).
Pulled, thanks Kalle.
prev parent reply other threads:[~2017-07-29 22:30 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
2017-07-29 22:30 ` David Miller [this message]
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=20170729.153042.505134537790079396.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kvalo@qca.qualcomm.com \
--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