All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Richard Weinberger <richard@nod.at>,
	David Miller <davem@davemloft.net>,
	Richard Cochran <richardcochran@gmail.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] drivers/ptp/Kconfig: add "depends on HAS_IOMEM" for 'PTP_1588_CLOCK_PCH'
Date: Tue, 02 Jul 2013 08:57:24 +0800	[thread overview]
Message-ID: <51D22574.60401@asianux.com> (raw)
In-Reply-To: <CAMuHMdXSExr0w-occZyHgj8o87q4_+BRH7e-bktMRfqfTqk8vQ@mail.gmail.com>

On 07/01/2013 07:19 PM, Geert Uytterhoeven wrote:
> On Mon, Jul 1, 2013 at 1:12 PM, Richard Weinberger <richard@nod.at> wrote:
>> > Am 01.07.2013 09:56, schrieb Geert Uytterhoeven:
>>> >> If we follow your reasoning, we can add dummy variants of all hardware support
>>> >> that lives in arch/*/include/asm to asm-generic, so everything would compile
>>> >> for all platforms. But that's now what we want.
>> >
>> > I hope you meant *not* want?
> Sorry, s/now/not/

I can understand your feelings, I also can understand if none of my
patches for 'asm-generic' will be applied.

Most of patches for 'asm-generic' should be for 'important' (e.g. duty
definition: whether should support 'COMPILE_TEST', what's the meaning of
'generic').

But this kind of patches are not 'emergent', they need be given more
considerations (they are not for applying, the are for thinking).

For duty definition, it is not for what we want to do, it is for what we
should do (or what we have to do).


At last, I will send related patches for 'COMPILE_TEST' (I can
understand if not applied, or no response). And also should send another
patch for HAS_IOMEM about ptp driver (also cc to you all).

Thanks.
-- 
Chen Gang

      reply	other threads:[~2013-07-02  0:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27  0:52 [PATCH] drivers/ptp/Kconfig: add "depends on HAS_IOMEM" for 'PTP_1588_CLOCK_PCH' Chen Gang
2013-06-27  6:48 ` Geert Uytterhoeven
2013-06-27  8:21   ` Chen Gang
2013-06-29  4:23 ` David Miller
2013-07-01  1:34   ` Chen Gang
2013-07-01  5:40     ` Richard Weinberger
2013-07-01  6:09       ` Chen Gang
2013-07-01  6:34         ` Richard Weinberger
2013-07-01  6:44           ` Chen Gang
2013-07-01  7:32             ` Geert Uytterhoeven
2013-07-01  7:47               ` Chen Gang
2013-07-01  7:56                 ` Geert Uytterhoeven
2013-07-01  8:17                   ` Chen Gang
2013-07-01 11:12                   ` Richard Weinberger
2013-07-01 11:19                     ` Geert Uytterhoeven
2013-07-02  0:57                       ` Chen Gang [this message]

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=51D22574.60401@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=davem@davemloft.net \
    --cc=geert@linux-m68k.org \
    --cc=netdev@vger.kernel.org \
    --cc=richard@nod.at \
    --cc=richardcochran@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.