mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: haicheng.li@linux.intel.com
Cc: netdev@vger.kernel.org, tshimizu818@gmail.com,
	linux-kernel@vger.kernel.org, haicheng.lee@gmail.com
Subject: Re: [PATCH 1/2] Fix build error caused by broken PCH_PTP module dependency.
Date: Thu, 27 Sep 2012 18:09:42 -0400 (EDT)	[thread overview]
Message-ID: <20120927.180942.969924012897168294.davem@davemloft.net> (raw)
In-Reply-To: <5060F97F.3040809@linux.intel.com>

From: Haicheng Li <haicheng.li@linux.intel.com>
Date: Tue, 25 Sep 2012 08:23:27 +0800

> From 898e3214b3406c620571cedf704719784b0df049 Mon Sep 17 00:00:00 2001
> From: Haicheng Li <haicheng.li@linux.intel.com>
> Date: Mon, 24 Sep 2012 15:52:30 +0800
> Subject: [PATCH 1/2] Fix build error caused by broken PCH_PTP module
> dependency.
> 
> The .config is:
>         CONFIG_PCH_GBE=y
>         CONFIG_PCH_PTP=y
>         CONFIG_PTP_1588_CLOCK=m
> 
> The build error:

Your patch submissions are of a very low quality.

And the main reason is that you microscopically look at problems and
do not investigate how the same thing might be handled elsewhere.

Therefore you will never become accustomed to the proper way problems
are fixed, and the proper way to submit patches.

Look at how other people submit patches, do any other patch submissions
look like your's having all of this metadata in the message body:

> From 898e3214b3406c620571cedf704719784b0df049 Mon Sep 17 00:00:00 2001
> From: Haicheng Li <haicheng.li@linux.intel.com>
> Date: Mon, 24 Sep 2012 15:52:30 +0800
> Subject: [PATCH 1/2] Fix build error caused by broken PCH_PTP module
> dependency.

No, nobody else does this.

As for this specific patch:

> -	depends on PTP_1588_CLOCK_PCH
> +	depends on PTP_1588_CLOCK_PCH = PCH_GBE

This is not the correct way to ensure that the module'ness of one
config option meets the module'ness requirements of another.

The correct way is to say something like "&& (PCH_GBE || PCH_GBE=n)"

  reply	other threads:[~2012-09-27 22:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-24  7:20 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
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 [this message]
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=20120927.180942.969924012897168294.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=haicheng.lee@gmail.com \
    --cc=haicheng.li@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®