netdev - Re: [Uclinux-dist-devel] [PATCH] can: bfin_can: switch to common Blackfin can header

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8bd0f97a1003162225i439d9900mfdc03eca5de0ff6e@mail.gmail.com>
Date:	Wed, 17 Mar 2010 01:25:39 -0400
From:	Mike Frysinger <vapier.adi@...il.com>
To:	David Miller <davem@...emloft.net>
Cc:	socketcan-core@...ts.berlios.de, netdev@...r.kernel.org,
	uclinux-dist-devel@...ckfin.uclinux.org,
	oliver.hartkopp@...kswagen.de, urs.thuermann@...kswagen.de
Subject: Re: [Uclinux-dist-devel] [PATCH] can: bfin_can: switch to common 
	Blackfin can header

On Wed, Mar 17, 2010 at 01:02, David Miller wrote:
> From: Mike Frysinger <vapier.adi@...il.com>
>> On Wed, Mar 17, 2010 at 00:28, David Miller wrote:
>>> From: Mike Frysinger <vapier@...too.org>
>>>> The MMR bits are being moved to this header, so include it.
>>>
>>> I can't actually apply this since this asm/bfin_can.h header
>>> doesn't even exist in the tree yet so this change will
>>> break the build.
>>
>> Linus was supposed to pull my tree, but if that isnt going to happen
>> for 2.6.34, then just apply the patch for 2.6.35
>
> That's what I was going to do, apply it to net-next-2.6
> but I can't even do that until the asm/bfin_can.h change
> appears in Linus's tree.

if the next tree is merged into linux-next, then the header is already there
-mike
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html