From: Oliver Hartkopp <socketcan@hartkopp.net>
To: David Miller <davem@davemloft.net>
Cc: mkl@pengutronix.de, netdev@vger.kernel.org, linux-can@vger.kernel.org
Subject: Re: pull-request: can-next 2013-01-26
Date: Mon, 28 Jan 2013 06:58:29 +0100 [thread overview]
Message-ID: <51061385.9070108@hartkopp.net> (raw)
In-Reply-To: <20130128.002455.638752456075920210.davem@davemloft.net>
On 28.01.2013 06:24, David Miller wrote:
> From: Marc Kleine-Budde <mkl@pengutronix.de>
> Date: Sat, 26 Jan 2013 17:09:07 +0100
>
>> this is a pull-request for net-next/master. There is are 9 patches by
>> Fabio Baltieri and Kurt Van Dijck which add LED infrastructure and
>> support for CAN devices. Bernd Krumboeck adds a driver for the USB CAN
>> adapter from 8 devices. Oliver Hartkopp improves the CAN gateway
>> functionality. There are 4 patches by me, which clean up the CAN's
>> Kconfig.
>
> Pulled, although:
>
> 1) You need to create an accessor helper for that can_skb_priv
> thing, every access to it is that horrible cast expression.
Ok, will do.
>
> 2) There is no reason to accomodate out of tree stuff, and for that
> reason I see no reason why you should need that headroom size
> check at all.
>
> Either the driver uses alloc_can_skb() or it does it's own SKB
> allocation and in-tree you've fixed that.
>
> You're just asking for trouble by trying to accomodate out of
> tree guys anyways, why if they create a headroom that happens
> to be the size of can_skb_priv. See what a joke that test is?
> It's not really protecting fully against anything.
I see.
I'll remove the check and try to inform the few out of tree guys that i'm
aware of.
Thanks,
Oliver
prev parent reply other threads:[~2013-01-28 5:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 16:09 pull-request: can-next 2013-01-26 Marc Kleine-Budde
2013-01-28 5:24 ` David Miller
2013-01-28 5:58 ` Oliver Hartkopp [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=51061385.9070108@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=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).