From: David Miller <davem@davemloft.net>
To: jie.yang@atheros.com
Cc: Luis.Rodriguez@Atheros.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next]atl1c: Add AR8151 v2 support and change L0s/L1 routine
Date: Sat, 29 May 2010 00:06:04 -0700 (PDT) [thread overview]
Message-ID: <20100529.000604.58441219.davem@davemloft.net> (raw)
In-Reply-To: <12750324381174-git-send-email-jie.yang@atheros.com>
From: <jie.yang@atheros.com>
Date: Fri, 28 May 2010 15:40:38 +0800
> From: Jie.Yang@atheros.com
>
> Add AR8151 v2.0 Gigabit 1000 support
> Change jumbo frame size to 6K
> Update L0s/L1 rountine
> Update atl1c_suspend routine.
>
> Signed-off-by: Jie.Yang@atheros.com
Your commit log message is way too terse.
You should describe in detail what your changes are.
Saying "Update L0s/L1 routine" doesn't tell us exactly what change
you are making. And more importantly, it does not tell us why you
are making this change.
This also applied to "update atl1c_suspend routine" You have to
list exactly change you are making, and why.
You should be able to write a full paragraph explaining what each
change is, and the reason for that change. This means 4 to 5 full
english sentences, which means more than 3 or 4 words in each
sentence.
Do not try to put as minimal amount of information into your commit
messages as possible, instead strive to put too much information.
Be long winded, and verbose, because you cannot predict what details
of your change and reasoning will be important to someone in the future.
Because some day someone will read your commit patch and wonder the
reasons why you made your changes.
I am not applying this patch until the commit message is made more
verbose and reasonable.
next prev parent reply other threads:[~2010-05-29 7:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 7:40 [PATCH net-next]atl1c: Add AR8151 v2 support and change L0s/L1 routine jie.yang
2010-05-29 7:06 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-31 6:42 jie.yang
2010-06-01 7:28 ` 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=20100529.000604.58441219.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Luis.Rodriguez@Atheros.com \
--cc=jie.yang@atheros.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).