linux-kernel - Re: [PATCH 1/1 net-next] ieee802154: fix _

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 01 Oct 2014 02:02:51 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	marcel@...tmann.org
Cc:	fabf@...net.be, linux-kernel@...r.kernel.org, alex.aring@...il.com,
	linux-wpan@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH 1/1 net-next] ieee802154: fix __init functions

From: Marcel Holtmann <marcel@...tmann.org>
Date: Wed, 1 Oct 2014 07:34:39 +0200

> Hi Fabian,
> 
>> Commit 3243acd37fd9
>> ("ieee802154: add __init to lowpan_frags_sysctl_register")
>> 
>> added __init to lowpan_frags_ns_sysctl_register instead of
>> lowpan_frags_sysctl_register
>> 
>> Suggested-by: Alexander Aring <alex.aring@...il.com>
>> Signed-off-by: Fabian Frederick <fabf@...net.be>
>> ---
>> net/ieee802154/reassembly.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
> 
> when trying to apply this to bluetooth-next kernel, I am getting this:
> 
> Applying: ieee802154: fix __init functions
> error: patch failed: net/ieee802154/reassembly.c:498
> error: net/ieee802154/reassembly.c: patch does not apply
> Patch failed at 0001 ieee802154: fix __init functions

You haven't been following the conversation.

I already applied his previous patch which had errors to net-next,
so this is a patch relative to net-next which fixes things and
implements the change correctly.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/