From: "Arend van Spriel" <arend@broadcom.com>
To: "Hauke Mehrtens" <hauke@hauke-m.de>,
"Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: backports@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] backport: need reinit_completion() for kernel before v3.13
Date: Mon, 25 Nov 2013 17:48:55 +0100 [thread overview]
Message-ID: <52937F77.9090701@broadcom.com> (raw)
In-Reply-To: <52933600.4020406@hauke-m.de>
On 11/25/2013 12:35 PM, Hauke Mehrtens wrote:
> On 11/25/2013 12:07 PM, Arend van Spriel wrote:
>> The use of INIT_COMPLETION() has been replaced by reinit_completion()
>> in v3.13-rc1. This patch backports that inline function.
>>
>> Cc: <linux-wireless@vger.kernel.org>
>> Signed-off-by: Arend van Spriel <arend@broadcom.com>
>> ---
>> backport/backport-include/linux/completion.h | 29 ++++++++++++++++++++++++++
>> 1 file changed, 29 insertions(+)
>> create mode 100644 backport/backport-include/linux/completion.h
>>
>
> This was already added in this commit:
> https://github.com/hauke/backports/commit/d9cb7a967513482c399d44e390429cea3de1d86d
>
> You should use backports for this repository:
> https://github.com/hauke/backports.git
Ok. With my fingers crossed: Did you also solve the whole genl patch
series that Johannes did in net-next?
Gr. AvS
> Hauke
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-11-25 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 11:07 [PATCH] backport: need reinit_completion() for kernel before v3.13 Arend van Spriel
2013-11-25 11:35 ` Hauke Mehrtens
2013-11-25 16:48 ` Arend van Spriel [this message]
2013-11-25 16:52 ` Hauke Mehrtens
2013-11-25 17:45 ` Arend van Spriel
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=52937F77.9090701@broadcom.com \
--to=arend@broadcom.com \
--cc=backports@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.