public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Henrik Kretzschmar <henne@nachtwindheim.de>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com, x86@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 1/7] x86: remove superflous goal definition of tsc_sync
Date: Fri, 04 Mar 2011 16:57:06 +0100	[thread overview]
Message-ID: <4D710BD2.3070303@nachtwindheim.de> (raw)
In-Reply-To: <AANLkTimptB1K3Kc+Hy1JbY=38pHSp0FfjA1LAKniLV2m@mail.gmail.com>

Am 04.03.2011 13:50, schrieb Cyrill Gorcunov:
>> Probably we better write it this way:
>>
>> - obj-$(CONFIG_SMP)              += smpboot.o tsc_sync.o
>> - obj-$(CONFIG_X86_64_SMP)       += tsc_sync.o
>>
>> + obj-$(CONFIG_SMP)              += smpboot.o
>> + obj-$(CONFIG_SMP)              += tsc_sync.o
>>
 
Yes, I see what you mean. Removing/adding one item on such a multiple item
line makes muddled diffs.

Thank you for friendly reviewing, patience and your Acked-by,

Henrik Kretzschmar



      reply	other threads:[~2011-03-04 15:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04 11:58 [PATCHv2 1/7] x86: remove superflous goal definition of tsc_sync Henrik Kretzschmar
2011-03-04 11:58 ` [PATCHv2 2/7] x86: make some apic symbols init Henrik Kretzschmar
2011-03-04 11:58 ` [PATCHv2 3/7] x86: make apic_disable() static and init Henrik Kretzschmar
2011-03-04 11:58 ` [PATCHv2 4/7] x86: remove enable_NMI_through_LVT0() entirely Henrik Kretzschmar
2011-03-04 11:58 ` [PATCHv2 5/7] x86: remove ancient crufty prototype Henrik Kretzschmar
2011-03-04 11:58 ` [PATCHv2 6/7] x86: remove unneeded prototypes Henrik Kretzschmar
2011-03-04 11:58 ` [PATCHv2 7/7] x86: fix section of a disable_apic_timer Henrik Kretzschmar
2011-03-04 12:03 ` [PATCHv2 1/7] x86: remove superflous goal definition of tsc_sync Ingo Molnar
2011-03-04 12:43 ` Cyrill Gorcunov
2011-03-04 12:50   ` Cyrill Gorcunov
2011-03-04 15:57     ` Henrik Kretzschmar [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=4D710BD2.3070303@nachtwindheim.de \
    --to=henne@nachtwindheim.de \
    --cc=gorcunov@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=x86@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