All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Einon <mark.einon@gmail.com>
To: gregkh@suse.de
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	o.hartmann@telovital.com, Mark Einon <mark.einon@gmail.com>
Subject: [PATCH 2/2] staging: et131x: Amend README file
Date: Sat,  3 Sep 2011 12:49:07 +0100	[thread overview]
Message-ID: <1315050547-4781-2-git-send-email-mark.einon@gmail.com> (raw)
In-Reply-To: <1315050547-4781-1-git-send-email-mark.einon@gmail.com>

I think the kernel style cleanups are done now.
Adding myself as a recipient of patches.

Signed-off-by: Mark Einon <mark.einon@gmail.com>
---
 drivers/staging/et131x/README |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/staging/et131x/README b/drivers/staging/et131x/README
index 28752a5..c6bcc6a 100644
--- a/drivers/staging/et131x/README
+++ b/drivers/staging/et131x/README
@@ -9,7 +9,6 @@ Note, the powermanagement options were removed from the vendor provided
 driver as they did not build properly at the time.
 
 TODO:
-	- kernel coding style cleanups
 	- forward port for latest network driver changes
 	- kill useless typecasts (e.g. in et1310_phy.c)
 	- alloc_etherdev is initializing memory with zero?!?
@@ -19,6 +18,7 @@ TODO:
 
 Please send patches to:
 	Greg Kroah-Hartman <gregkh@suse.de>
+	Mark Einon <mark.einon@gmail.com>
 
 And Cc: Olaf Hartmann <o.hartmann@telovital.com> as he has this device and can
 test any changes.
-- 
1.7.6


  reply	other threads:[~2011-09-03 11:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-03 11:49 [PATCH 1/2] staging: et131x: Fix checkpatch whitespace warnings Mark Einon
2011-09-03 11:49 ` Mark Einon [this message]
2011-09-10  5:22 ` Dan Carpenter
2011-09-10 16:34   ` Mark Einon
2011-09-10  5:41 ` Joe Perches
2011-09-10 16:40   ` Mark Einon

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=1315050547-4781-2-git-send-email-mark.einon@gmail.com \
    --to=mark.einon@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=o.hartmann@telovital.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.