socketcan-core  

Messages by Thread

• [PATCH net-next-2.6 8/17 v2] can: EG20T PCH: Change Copyright and module description Tomoya MORINAGA
  • [PATCH net-next-2.6 8/17 v2] can: EG20T PCH: Change Copyright and module description Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 8/17 v2] can: EG20T PCH: Change Copyright and module description Marc Kleine-Budde
  • Re: [PATCH net-next-2.6 8/17 v2] can: EG20T PCH: Change Copyright and module description Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 8/17 v2] can: EG20T PCH: Change Copyright and module description Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 8/17 v2] can: EG20T PCH: Change Copyright and module description Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 8/17 v2] can: EG20T PCH: Change Copyright and module description Marc Kleine-Budde
  • Re: [PATCH net-next-2.6 8/17 v2] can: EG20T PCH: Change Copyright and module description Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 8/17 v2] can: EG20T PCH: Change Copyright and module description Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 8/17 v2] can: EG20T PCH: Change Copyright and module description Marc Kleine-Budde
  • Re: [PATCH net-next-2.6 8/17 v2] can: EG20T PCH: Change Copyright and module description Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 8/17 v2] can: EG20T PCH: Change Copyright and module description Marc Kleine-Budde
  • Re: [PATCH net-next-2.6 8/17 v2] can: EG20T PCH: Change Copyright and module description Tomoya MORINAGA
• [PATCH net-next-2.6 7/17 v2] can: EG20T PCH: Modify function/macro name/type Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 7/17 v2] can: EG20T PCH: Modify function/macro name/type David Miller
  • Re: [PATCH net-next-2.6 7/17 v2] can: EG20T PCH: Modify function/macro name/type Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 7/17 v2] can: EG20T PCH: Modify function/macro name/type David Miller
  • Re: [PATCH net-next-2.6 7/17 v2] can: EG20T PCH: Modify function/macro name/type Tomoya MORINAGA
• Re: [PATCH 00/62] drivers/net: Use static const David Miller
  • Re: [PATCH 00/62] drivers/net: Use static const David Miller
  • Re: [PATCH 00/62] drivers/net: Use static const David Miller
• [PATCH net-next-2.6 17/17] can: EG20T PCH: Optimize "if" condition in rx/tx processing Tomoya MORINAGA
• [PATCH net-next-2.6 16/17] can: EG20T PCH: Fix incorrect return processing Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 16/17] can: EG20T PCH: Fix incorrect return processing Marc Kleine-Budde
• [PATCH net-next-2.6 15/17] can: EG20T PCH: Move MSI processing open/close to probe/remove Tomoya MORINAGA
• [PATCH net-next-2.6 14/17] can: EG20T PCH: Comment optimization Tomoya MORINAGA
• [PATCH net-next-2.6 13/17] can: EG20T PCH: Fix miss-setting status issue Tomoya MORINAGA
• [PATCH net-next-2.6 12/17] can: EG20T PCH: Fix bit timing calculation issue Tomoya MORINAGA
• [PATCH net-next-2.6 11/17] can: EG20T PCH: Delete unnecessary/redundant code Tomoya MORINAGA
• [PATCH net-next-2.6 10/17] can: EG20T PCH: Fix coding rule violation Tomoya MORINAGA
• [PATCH net-next-2.6 9/17] can: EG20T PCH: Use netdev_dbg instead of dev_dbg Tomoya MORINAGA
• [PATCH net-next-2.6 8/17] can: EG20T PCH: Change Copyright and module description Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 8/17] can: EG20T PCH: Change Copyright and module description David Miller
• [PATCH net-next-2.6 7/17] can: EG20T PCH: Rename function/macro name Tomoya MORINAGA
• [PATCH net-next-2.6 6/17] can: EG20T PCH: Fix endianness issue Tomoya MORINAGA
• [PATCH net-next-2.6 5/17] can: EG20T PCH: Delete unnecessary spin_lock Tomoya MORINAGA
• [PATCH net-next-2.6 4/17] can: EG20T PCH: Add Tx Flow Control Tomoya MORINAGA
• [PATCH net-next-2.6 3/17] can: EG20T PCH: Enumerate some macros Tomoya MORINAGA
• [PATCH net-next-2.6 2/17] can: EG20T PCH: Change Message Object Index Tomoya MORINAGA
• [PATCH net-next-2.6 1/17] can: EG20T PCH: Separate Interface Register(IF1/IF2) Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 1/17] can: EG20T PCH: Separate Interface Register(IF1/IF2) Marc Kleine-Budde
• Re: [PATCH 09/14] drivers/net/can/sja1000: Use printf extension %pR for struct resource David Miller
• [PATCH net-next-2.6] can: EG20T PCH: use BIT(X) Tomoya MORINAGA
  • Re: [PATCH net-next-2.6] can: EG20T PCH: use BIT(X) Marc Kleine-Budde
  • [PATCH net-next-2.6] can: EG20T PCH: use BIT(X) Tomoya MORINAGA
  • Re: [PATCH net-next-2.6] can: EG20T PCH: use BIT(X) David Miller
• [PATCH net-next-2.6 v2] can: EG20T PCH: add prefix to macro Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 v2] can: EG20T PCH: add prefix to macro David Miller
• [PATCH net-next-2.6 ] can: EG20T PCH: add prefix to macro Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 ] can: EG20T PCH: add prefix to macro Marc Kleine-Budde
• Re: [PATCH net-next-2.6 v4] can: Topcliff: PCH_CAN driver: Add Flow control/Fix Endianess issue/Separate IF register/Enumerate LEC macro/Move MSI processing/Use BIT(X)/Change Message Object index/Add prefix PCH_ David Miller
  • Re: [PATCH net-next-2.6 v4] can: Topcliff: PCH_CAN driver: Add Flow control/Fix Endianess issue/Separate IF register/Enumerate LEC macro/Move MSI processing/Use BIT(X)/Change Message Object index/Add prefix PCH_ Wolfgang Grandegger
  • Re: [PATCH net-next-2.6 v4] can: Topcliff: PCH_CAN driver: Add Flow control/Fix Endianess issue/Separate IF register/Enumerate LEC macro/Move MSI processing/Use BIT(X)/Change Message Object index/Add prefix PCH_ David Miller
  • Re: [PATCH net-next-2.6 v4] can: Topcliff: PCH_CAN driver: Add Flow control/Fix Endianess issue/Separate IF register/Enumerate LEC macro/Move MSI processing/Use BIT(X)/Change Message Object index/Add prefix PCH_ Wolfram Sang
  • Re: [PATCH net-next-2.6 v4] can: Topcliff: PCH_CAN driver: Add Flow control/Fix Endianess issue/Separate IF register/Enumerate LEC macro/Move MSI processing/Use BIT(X)/Change Message Object index/Add prefix PCH_ David Miller
  • Re: [PATCH net-next-2.6 v4] can: Topcliff: PCH_CAN driver: Add Flow control/Fix Endianess issue/Separate IF register/Enumerate LEC macro/Move MSI processing/Use BIT(X)/Change Message Object index/Add prefix PCH_ Tomoya MORINAGA
• Re: [PATCH net-next-2.6 v4] can: Topcliff: PCH_CAN driver: Add Flow control/Fix Endianess issue/Separate IF register/Enumerate LEC macro/Move MSI processing/Use BIT(X)/Change Message Object index/Add prefix PCH_ Wolfgang Grandegger
• [PATCH net-next-2.6 v3] can: Topcliff: PCH_CAN driver: Add Flow control, Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 v3] can: Topcliff: PCH_CAN driver: Add Flow control, Wolfgang Grandegger
  • Re: [PATCH net-next-2.6 v3] can: Topcliff: PCH_CAN driver: Add Flow control, Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 v3] can: Topcliff: PCH_CAN driver: Add Flow control, Marc Kleine-Budde
  • Re: [PATCH net-next-2.6 v3] can: Topcliff: PCH_CAN driver: Add Flow control, Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 v3] can: Topcliff: PCH_CAN driver: Add Flow control, Marc Kleine-Budde
  • Re: [PATCH net-next-2.6 v3] can: Topcliff: PCH_CAN driver: Add Flow control, Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 v3] can: Topcliff: PCH_CAN driver: Add Flow control, Marc Kleine-Budde
  • Re: [PATCH net-next-2.6 v3] can: Topcliff: PCH_CAN driver: Add Flow control, Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 v3] can: Topcliff: PCH_CAN driver: Add Flow control, Marc Kleine-Budde
  • Re: [PATCH net-next-2.6 v3] can: Topcliff: PCH_CAN driver: Add Flow control, Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 v3] can: Topcliff: PCH_CAN driver: Add Flow control, Marc Kleine-Budde
• [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Add Flow control, Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Add Flow control, Marc Kleine-Budde
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Add Flow control, Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Add Flow control, Marc Kleine-Budde
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Add Flow control, Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Add Flow control, David Miller
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Add Flow control, Wolfgang Grandegger
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Add Flow control, Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Add Flow control, Wolfgang Grandegger
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Add Flow control, Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Add Flow control, Wolfgang Grandegger
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Add Flow control, Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Add Flow control, Tomoya MORINAGA
• Re: [PATCH 4/10] Fix leaking of kernel heap addresses in net/ David Miller
  • Re: [PATCH 4/10] Fix leaking of kernel heap addresses in net/ David Miller
  • Re: [PATCH 4/10] Fix leaking of kernel heap addresses in net/ David Miller
  • Re: [PATCH 4/10] Fix leaking of kernel heap addresses in net/ David Miller
  • Re: [PATCH 4/10] Fix leaking of kernel heap addresses in net/ David Miller
• [PATCH 00/39] Cleanup WARN #defines Joe Perches
  • [PATCH 16/39] drivers/net/can: Update WARN uses Joe Perches
  • Re: [PATCH 16/39] drivers/net/can: Update WARN uses David Miller
• RFC can: do not expose kernel addresses via procfs Oliver Hartkopp
• [PATCH] ICPDAS: Add support for ICPDAS PCI/104 CAN boards Wayne Lin
  • [PATCH] ICPDAS: Add support for ICPDAS PCI/104 CAN boards Wayne Lin
  • Re: [PATCH] ICPDAS: Add support for ICPDAS PCI/104 CAN boards Wolfgang Grandegger
  • [PATCH] ICPDAS: Add support for ICPDAS PCI/104 CAN boards Wayne Lin
  • [PATCH] ICPDAS: Add support for ICPDAS PCI/104 CAN boards Wayne Lin
• CAN procfs rework Oliver Hartkopp
  • Re: CAN procfs rework Marc Kleine-Budde
  • Re: CAN procfs rework Urs Thuermann
  • Re: CAN procfs rework Marc Kleine-Budde
  • Re: CAN procfs rework Oliver Hartkopp
  • Re: CAN procfs rework Kurt Van Dijck
  • Re: CAN procfs rework Marc Kleine-Budde
• Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Tomoya
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Marc Kleine-Budde
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Marc Kleine-Budde
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Wolfgang Grandegger
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Marc Kleine-Budde
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Wolfgang Grandegger
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Wolfgang Grandegger
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Marc Kleine-Budde
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Oliver Hartkopp
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Marc Kleine-Budde
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Marc Kleine-Budde
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Marc Kleine-Budde
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Marc Kleine-Budde
• [PATCH 0/2] can: pch_can: fix sparse warnings and section mismatch Marc Kleine-Budde
  • [PATCH 2/2] can: pch_can: fix section mismatch warning by using a whitelisted name Marc Kleine-Budde
  • Re: [PATCH 2/2] can: pch_can: fix section mismatch warning by using a whitelisted name David Miller
  • [PATCH 1/2] can: pch_can: fix sparse warning Marc Kleine-Budde
  • Re: [PATCH 1/2] can: pch_can: fix sparse warning David Miller
• Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings David Miller
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings David Miller
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings David Miller
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Wolfgang Grandegger
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Marc Kleine-Budde
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix buildwarnings Tomoya MORINAGA
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix buildwarnings Wolfgang Grandegger
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix buildwarnings Marc Kleine-Budde
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix buildwarnings Marc Kleine-Budde
  • Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Tomoya MORINAGA
  • can: About Socket CAN with MSI issue Tomoya MORINAGA
  • Re: can: About Socket CAN with MSI issue Wolfgang Grandegger
  • Re: can: About Socket CAN with MSI issue Tomoya MORINAGA
• Re: [PATCH net-next-2.6 v2] can: Topcliff: Update PCH_CAN driver to 2.6.36 David Miller
• [PATCH V2 0/8] don't copy data to rx'ed RTR frames Marc Kleine-Budde
  • [PATCH 1/8] can: at91_can: don't copy data to rx'ed RTR frames Marc Kleine-Budde
  • [PATCH 2/8] can: bfin_can: don't copy data to rx'ed RTR frames Marc Kleine-Budde
  • [PATCH 3/8] can: flexcan: don't copy data to rx'ed RTR frames Marc Kleine-Budde
  • [PATCH 5/8] can: mcp251x: don't copy data to rx'ed RTR frames Marc Kleine-Budde
  • [PATCH V2 6/8] can: ti_hecc: don't copy data to rx'ed RTR frames Marc Kleine-Budde
  • [PATCH V2 7/8] can: janz-ican3: cleanup of ican3_to_can_frame and can_frame_to_ican3 Marc Kleine-Budde
  • [PATCH 4/8] can: sja1000: don't copy data to rx'ed RTR frames Marc Kleine-Budde
  • [PATCH 8/8] can: janz-ican3: don't copy data to rx'ed RTR frames Marc Kleine-Budde
• [PATCH/RFC 0/8] don't copy data to rx'ed RTR frames Marc Kleine-Budde
  • [PATCH 2/8] can: bfin_can: don't copy data to rx'ed RTR frames Marc Kleine-Budde
  • [PATCH 3/8] can: flexcan: don't copy data to rx'ed RTR frames Marc Kleine-Budde
  • [PATCH 6/8] can: ti_hecc: don't copy data to rx'ed RTR frames Marc Kleine-Budde
  • Re: [PATCH 6/8] can: ti_hecc: don't copy data to rx'ed RTR frames Oliver Hartkopp
  • Re: [PATCH 6/8] can: ti_hecc: don't copy data to rx'ed RTR frames Marc Kleine-Budde
  • [PATCH 5/8] can: mcp251x: don't copy data to rx'ed RTR frames Marc Kleine-Budde
  • [PATCH 4/8] can: sja1000: don't copy data to rx'ed RTR frames Marc Kleine-Budde
  • [PATCH 7/8] can: janz-ican3: cleanup of ican3_to_can_frame Marc Kleine-Budde
  • Re: [PATCH 7/8] can: janz-ican3: cleanup of ican3_to_can_frame Ira W. Snyder
  • Re: [PATCH 7/8] can: janz-ican3: cleanup of ican3_to_can_frame Marc Kleine-Budde
  • Re: [PATCH 7/8] can: janz-ican3: cleanup of ican3_to_can_frame Ira W. Snyder
  • Re: [PATCH 7/8] can: janz-ican3: cleanup of ican3_to_can_frame Wolfram Sang
  • Re: [PATCH 7/8] can: janz-ican3: cleanup of ican3_to_can_frame Marc Kleine-Budde
  • Re: [PATCH 7/8] can: janz-ican3: cleanup of ican3_to_can_frame Wolfram Sang
  • Re: [PATCH 7/8] can: janz-ican3: cleanup of ican3_to_can_frame Marc Kleine-Budde
  • [PATCH 8/8] can: janz-ican3: don't copy data to rx'ed RTR frames Marc Kleine-Budde
  • Re: [PATCH 8/8] can: janz-ican3: don't copy data to rx'ed RTR frames Ira W. Snyder
  • [PATCH 1/8] can: at91_can: don't copy data to rx'ed RTR frames Marc Kleine-Budde
  • Re: [PATCH/RFC 0/8] don't copy data to rx'ed RTR frames Wolfgang Grandegger
  • Re: [PATCH/RFC 0/8] don't copy data to rx'ed RTR frames Kurt Van Dijck
  • Re: [PATCH/RFC 0/8] don't copy data to rx'ed RTR frames Marc Kleine-Budde
  • Re: [PATCH/RFC 0/8] don't copy data to rx'ed RTR frames Kurt Van Dijck
• [PATCH] can: mcp251x: fix reception of standard RTR frames Marc Kleine-Budde
  • Re: [PATCH] can: mcp251x: fix reception of standard RTR frames David Miller
• [PATCH] can: flexcan: fix use after free of priv Marc Kleine-Budde
  • Re: [PATCH] can: flexcan: fix use after free of priv David Miller
• [RFC] CAN frames with RTR and dlc != 0 Marc Kleine-Budde
  • Re: [RFC] CAN frames with RTR and dlc != 0 Kurt Van Dijck
  • Re: [RFC] CAN frames with RTR and dlc != 0 Gerhard Uttenthaler
  • Re: [RFC] CAN frames with RTR and dlc != 0 Gerhard Uttenthaler
  • Re: [RFC] CAN frames with RTR and dlc != 0 Marc Kleine-Budde
  • Re: [RFC] CAN frames with RTR and dlc != 0 Oliver Hartkopp
  • Re: [RFC] CAN frames with RTR and dlc != 0 Oliver Hartkopp
  • Re: [RFC] CAN frames with RTR and dlc != 0 Marc Kleine-Budde
  • Re: [RFC] CAN frames with RTR and dlc != 0 Kurt Van Dijck
  • Re: [RFC] CAN frames with RTR and dlc != 0 Marc Kleine-Budde
  • Re: [RFC] CAN frames with RTR and dlc != 0 Oliver Hartkopp
• [PATCH 00/10] can: at91: bugfixes and improvements Marc Kleine-Budde
  • [PATCH 02/10] can: at91_can: fix reception of extended frames Marc Kleine-Budde
  • [PATCH 01/10] can: at91_can: use correct bit to enable CAN_CTRLMODE_3_SAMPLES Marc Kleine-Budde
  • [PATCH 04/10] can: at91_can: fix compiler warning in at91_irq_err_state Marc Kleine-Budde
  • [PATCH 05/10] can: at91_can: fix section mismatch warning Marc Kleine-Budde
  • [PATCH 03/10] can: at91_can: fix use after free of priv Marc Kleine-Budde
  • [PATCH 06/10] can: at91_can: implement and use at91_get_berr_counter Marc Kleine-Budde
  • [PATCH 07/10] can: at91_can: set bittiming in chip_start Marc Kleine-Budde
  • [PATCH 09/10] can: at91_can: convert dev_<level> printing to netdev_<level> Marc Kleine-Budde
  • [PATCH 10/10] can: at91_can: add KBUILD_MODNAME to bittiming constant Marc Kleine-Budde

• Earlier messages
• Later messages