netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amos Kong <akong@redhat.com>
To: linux-m68k@vger.kernel.org
Cc: geert@linux-m68k.org, netdev@vger.kernel.org,
	davem@davemloft.net, schwab@linux-m68k.org
Subject: [PATCH 0/2] trivial cleanup
Date: Thu,  5 Jun 2014 11:01:20 +0800	[thread overview]
Message-ID: <1401937282-18345-1-git-send-email-akong@redhat.com> (raw)

I found the RAM size in comments isn't correct,
fix it.

Amos Kong (2):
  mvme147: fix ram size in comment
  hplance: fix ram size in comment

 drivers/net/ethernet/amd/hplance.c | 4 ++--
 drivers/net/ethernet/amd/mvme147.c | 6 +++---
 2 files changed, 5 insertions(+), 5 deletions(-)

-- 
1.9.3

             reply	other threads:[~2014-06-05  3:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05  3:01 Amos Kong [this message]
2014-06-05  3:01 ` [PATCH 1/2] mvme147: fix ram size in comment Amos Kong
2014-06-05  3:01 ` [PATCH 2/2] hplance: " Amos Kong
2014-06-05 22:14 ` [PATCH 0/2] trivial cleanup David Miller

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=1401937282-18345-1-git-send-email-akong@redhat.com \
    --to=akong@redhat.com \
    --cc=davem@davemloft.net \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=schwab@linux-m68k.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).