From: David Miller <davem@davemloft.net>
To: kvalo@codeaurora.org
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: pull-request: wireless-drivers-next 2017-04-03
Date: Tue, 04 Apr 2017 10:31:44 -0700 (PDT) [thread overview]
Message-ID: <20170404.103144.1438343234401389523.davem@davemloft.net> (raw)
In-Reply-To: <87a87xohpp.fsf@kamboji.qca.qualcomm.com>
From: Kalle Valo <kvalo@codeaurora.org>
Date: Mon, 03 Apr 2017 14:26:10 +0300
> here few really small fixes. I'm hoping this to be the last pull request
> for 4.11.
>
> Please let me if there are any problems.
Pulled, thanks.
But I will warn you, you say fixes, but your Subject line and
GIT tag says "-next" so I pulled it into net-next.
next prev parent reply other threads:[~2017-04-04 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 11:26 pull-request: wireless-drivers-next 2017-04-03 Kalle Valo
2017-04-04 17:31 ` David Miller [this message]
2017-04-04 17:48 ` Kalle Valo
2017-04-04 18:37 ` David Miller
2017-04-05 4:19 ` 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=20170404.103144.1438343234401389523.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kvalo@codeaurora.org \
--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).