From: Haicheng Li <haicheng.li@linux.intel.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, tshimizu818@gmail.com,
linux-kernel@vger.kernel.org, haicheng.lee@gmail.com
Subject: Re: [PATCH 2/2] Fix a typo in PTP_1588_CLOCK_PCH Kconfig help info.
Date: Fri, 28 Sep 2012 14:44:00 +0800 [thread overview]
Message-ID: <50654730.6010204@linux.intel.com> (raw)
In-Reply-To: <20120927.180640.447002776076460117.davem@davemloft.net>
On 09/28/2012 06:06 AM, David Miller wrote:
>> - will be called ptp_pch.
>> + will be called by pch_ptp.
>
> The original sentence is correct, it is stating the name of the module
> that will be built not the module that will call it.
You're right.
> Rather, the "pch_ptp" is what might need to be adjusted.
No need, the output is ptp_pch.ko.
So pls. ignore this patch. sorry for the bothering.
-haicheng
next prev parent reply other threads:[~2012-09-28 6:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 7:20 [PATCH 1/2] Fix build error caused by broken PCH_PTP module dependency Haicheng Li
2012-09-24 7:22 ` [PATCH 2/2] Fix wrong description in PTP_1588_CLOCK_PCH help info Haicheng Li
2012-09-24 8:14 ` [Updated PATCH 2/2] Fix a typo in PTP_1588_CLOCK_PCH Kconfig " Haicheng Li
2012-09-25 0:24 ` [PATCH " Haicheng Li
2012-09-27 22:06 ` David Miller
2012-09-28 6:44 ` Haicheng Li [this message]
2012-09-24 8:08 ` [Updated PATCH 1/2] Fix build error caused by broken PCH_PTP module dependency Haicheng Li
2012-09-24 17:46 ` [PATCH " David Miller
2012-09-25 0:23 ` Haicheng Li
2012-09-27 22:09 ` David Miller
2012-09-28 6:41 ` Haicheng Li
2012-09-28 6:46 ` David Miller
2012-09-28 6:57 ` Haicheng Li
2012-10-03 2:22 ` David Miller
2012-10-03 21:45 ` Ben Hutchings
2012-10-04 0:43 ` David Miller
2012-10-16 20:09 ` Ben Hutchings
2012-10-16 20:17 ` David Miller
2012-10-16 21:08 ` Keller, Jacob E
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=50654730.6010204@linux.intel.com \
--to=haicheng.li@linux.intel.com \
--cc=davem@davemloft.net \
--cc=haicheng.lee@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tshimizu818@gmail.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.