From: David Miller <davem@davemloft.net>
To: mkl@pengutronix.de
Cc: netdev@vger.kernel.org, linux-can@vger.kernel.org
Subject: Re: [PATCH] net: sched: enable CAN Identifier to be build into kernel
Date: Fri, 23 Nov 2012 14:22:58 -0500 (EST) [thread overview]
Message-ID: <20121123.142258.816355331172102352.davem@davemloft.net> (raw)
In-Reply-To: <1353667497-25676-1-git-send-email-mkl@pengutronix.de>
From: Marc Kleine-Budde <mkl@pengutronix.de>
Date: Fri, 23 Nov 2012 11:44:57 +0100
> This patch makes it possible to build the CAN Identifier into the kernel, even
> if the CAN support is build as a module.
>
> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Why is this so critical that you're asking me to merge this into
the 'net' tree mere days before Linus makes a release?
next prev parent reply other threads:[~2012-11-23 19:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 10:44 [PATCH] net: sched: enable CAN Identifier to be build into kernel Marc Kleine-Budde
2012-11-23 19:22 ` David Miller [this message]
2012-11-24 12:22 ` Marc Kleine-Budde
2012-11-25 21:06 ` 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=20121123.142258.816355331172102352.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--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).