From: Michal Simek <monstr@monstr.eu>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] net: emaclite: Add missing linux/interrupt.h header
Date: Thu, 09 Jun 2011 10:56:42 +0200 [thread overview]
Message-ID: <4DF08ACA.30507@monstr.eu> (raw)
In-Reply-To: <20110609.012944.602872260942727070.davem@davemloft.net>
David Miller wrote:
> From: Michal Simek <monstr@monstr.eu>
> Date: Thu, 9 Jun 2011 10:15:33 +0200
>
>> Log:
>> drivers/net/xilinx_emaclite.c: In function 'xemaclite_open':
>> drivers/net/xilinx_emaclite.c:961: error: implicit declaration of function 'request_irq'
>> drivers/net/xilinx_emaclite.c: In function 'xemaclite_close':
>> drivers/net/xilinx_emaclite.c:995: error: implicit declaration of function 'free_irq'
>> make[2]: *** [drivers/net/xilinx_emaclite.o] Error 1
>> make[1]: *** [drivers/net] Error 2
>> make: *** [drivers] Error 2
>>
>> Signed-off-by: Michal Simek <monstr@monstr.eu>
>
> This is only relevant for the -next tree, you should specify that when
> submitting patches otherwise the maintainer not apply the patch where
> it actually belongs.
sorry for that. Yes, it is for -next tree.
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
prev parent reply other threads:[~2011-06-09 8:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 8:15 [PATCH] net: emaclite: Add missing linux/interrupt.h header Michal Simek
2011-06-09 8:29 ` David Miller
2011-06-09 8:56 ` Michal Simek [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=4DF08ACA.30507@monstr.eu \
--to=monstr@monstr.eu \
--cc=davem@davemloft.net \
--cc=linux-kernel@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).