| 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
| ||
|
Date: Tue, 23 Aug 2011 23:40:32 +0100 From: Mark Einon <mark.einon@...il.com> To: gregkh@...e.de Cc: greg@...ah.com, devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org, o.hartmann@...ovital.com Subject: [PATCH 0/8] [RESEND] staging: et131x: Code cleanups As requested, resend patches not applied yet to staging-next, plus one new patch. Mark Einon (8): [PATCH 1/8] [RESEND] staging: et131x: Remove unecessary *etdev NULL check in [PATCH 2/8] [RESEND] staging: et131x: Converting et1310_tx.c function and [PATCH 3/8] [RESEND] staging: et131x: Converting et1310_adapter.h variable [PATCH 4/8] [RESEND] staging: et131x: Removing commented out code implemented [PATCH 5/8] [RESEND] staging: et131x: Rename var name 'etdev' to 'adapter' [PATCH 6/8] [RESEND] staging: et131x: Fix link detection signalling [PATCH 7/8] [RESEND] staging: et131x: Fix free IRQ from IRQ context warning [PATCH 8/8] staging: et131x: Update tx trans_start on device close drivers/staging/et131x/et1310_eeprom.c | 32 +- drivers/staging/et131x/et1310_mac.c | 243 ++++++++-------- drivers/staging/et131x/et1310_phy.c | 404 +++++++++++++-------------- drivers/staging/et131x/et1310_pm.c | 44 ++-- drivers/staging/et131x/et1310_rx.c | 188 +++++++------ drivers/staging/et131x/et1310_tx.c | 464 +++++++++++++++---------------- drivers/staging/et131x/et131x.h | 2 +- drivers/staging/et131x/et131x_adapter.h | 95 +++---- drivers/staging/et131x/et131x_initpci.c | 157 +++++------ drivers/staging/et131x/et131x_isr.c | 52 ++-- drivers/staging/et131x/et131x_netdev.c | 132 +++++---- 11 files changed, 892 insertions(+), 921 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists