From: David Miller <davem@davemloft.net>
To: marcel@holtmann.org
Cc: fabf@skynet.be, linux-kernel@vger.kernel.org,
alex.aring@gmail.com, linux-wpan@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 1/1 net-next] ieee802154: fix __init functions
Date: Wed, 01 Oct 2014 02:02:51 -0400 (EDT) [thread overview]
Message-ID: <20141001.020251.105468714011560897.davem@davemloft.net> (raw)
In-Reply-To: <56FE06A5-5C2A-42E4-B01A-15EB36BAADE5@holtmann.org>
From: Marcel Holtmann <marcel@holtmann.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@gmail.com>
>> Signed-off-by: Fabian Frederick <fabf@skynet.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.
next prev parent reply other threads:[~2014-10-01 6:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 5:27 [PATCH 1/1 net-next] ieee802154: fix __init functions Fabian Frederick
2014-10-01 5:34 ` Marcel Holtmann
2014-10-01 6:02 ` David Miller [this message]
2014-10-01 6:08 ` Alexander Aring
2014-10-01 6:03 ` 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=20141001.020251.105468714011560897.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alex.aring@gmail.com \
--cc=fabf@skynet.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=marcel@holtmann.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