From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oliver Hartkopp Subject: Re: [PATCH can-next v4] em_canid: Ematch rule to match CAN frames according to their identifiers Date: Fri, 06 Jul 2012 06:52:46 +0200 Message-ID: <4FF66F1E.5060203@hartkopp.net> References: <4FF3C2AE.9010106@hartkopp.net> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Return-path: Received: from mo-p00-ob.rzone.de ([81.169.146.160]:46298 "EHLO mo-p00-ob.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751956Ab2GFEwn (ORCPT ); Fri, 6 Jul 2012 00:52:43 -0400 In-Reply-To: <4FF3C2AE.9010106@hartkopp.net> Sender: linux-can-owner@vger.kernel.org List-ID: To: David Miller Cc: Marc Kleine-Budde , "linux-can@vger.kernel.org" , Rostislav Lisovy , Linux Netdev List On 04.07.2012 06:12, Oliver Hartkopp wrote: > This ematch makes it possible to classify CAN frames (AF_CAN) according > to their identifiers. This functionality can not be easily achieved with > existing classifiers, such as u32, because CAN identifier is always stored > in native endianness, whereas u32 expects Network byte order. > > Signed-off-by: Rostislav Lisovy > Signed-off-by: Oliver Hartkopp This patch is originally from Rostislav and is already part of this can-next pull request: http://marc.info/?l=linux-netdev&m=134141429413608&w=2 Tnx & regards, Oliver