linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Fabio Baltieri <fabio.baltieri@gmail.com>,
	kernel-janitors@vger.kernel.org, linux-can@vger.kernel.org
Subject: Re: [can:master 1/1] drivers/net/can/led.c:41:4: error: implicit declaration of function 'led_trigger_blink_oneshot'
Date: Wed, 01 Aug 2012 15:35:16 +0200	[thread overview]
Message-ID: <50193094.4090704@pengutronix.de> (raw)
In-Reply-To: <20120801125137.GB19751@localhost>

[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]

On 08/01/2012 02:51 PM, Fengguang Wu wrote:
> Hi Fabio,
> 
> Kernel build failed on
> 
> tree:   git://gitorious.org/linux-can/linux-can-next master
> head:   272669c35de610ef75427d2f41b328a5e0f65bfc
> commit: 272669c35de610ef75427d2f41b328a5e0f65bfc [1/1] can: add tx/rx LED trigger support
> config: i386-allmodconfig (attached as .config)
> 
> All related error/warning messages:
> 
> drivers/net/can/led.c: In function 'can_led_event':
> drivers/net/can/led.c:41:4: error: implicit declaration of function 'led_trigger_blink_oneshot' [-Werror=implicit-function-declaration]

We have to delay the patch until rc1 or whatever is merged back to net-next.

Or I will provide a temporary tree with current mainline as base.

Marc
-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

           reply	other threads:[~2012-08-01 13:35 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20120801125137.GB19751@localhost>]

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=50193094.4090704@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=fabio.baltieri@gmail.com \
    --cc=fengguang.wu@intel.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-can@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).