mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Suresh Siddha <suresh.b.siddha@intel.com>
To: Zachary Amsden <zach@vmware.com>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
	Yinghai Lu <yhlu.kernel@gmail.com>, Ingo Molnar <mingo@elte.hu>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
	Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [PATCH] x86: APIC: Remove apic_write_around(); use alternatives
Date: Fri, 18 Jul 2008 15:49:23 -0700	[thread overview]
Message-ID: <20080718224922.GB4507@linux-os.sc.intel.com> (raw)
In-Reply-To: <1216420937.30348.30.camel@bodhitayantram.eng.vmware.com>

On Fri, Jul 18, 2008 at 03:42:17PM -0700, Zachary Amsden wrote:
> On Fri, 2008-07-18 at 15:02 -0700, Maciej W. Rozycki wrote:
> > On Fri, 18 Jul 2008, Yinghai Lu wrote:
> >
> > >   CC      arch/x86/kernel/apic_64.o
> > > arch/x86/kernel/apic_64.c:170: error: unknown field 'write_atomic'
> > > specified in initializer
> > > arch/x86/kernel/apic_64.c:170: error: 'native_apic_mem_write_atomic'
> > > undeclared here (not in a function)
> > > arch/x86/kernel/apic_64.c:209: error: unknown field 'write_atomic'
> > > specified in initializer
> > > arch/x86/kernel/apic_64.c:209: warning: initialization from
> > > incompatible pointer type
> > > make[1]: *** [arch/x86/kernel/apic_64.o] Error 1
> > > make: *** [arch/x86/kernel] Error 2
> >
> >  Just remove the offending initialisers.  They are not needed anymore as
> > the .write method is now used universally including places where
> > .write_atomic was.  I just could not stand watching the thing
> > proliferate...
> 
> Thank you for cleaning this up Yinghai, but this really begs the
> question - is having write_atomic REALLY worthwhile?

And this thread is about,  Maciej's cleanup patch which removed
write_atomic completely :)

Thanks to Maciej who posted this fix. It was on my todo list for
sometime now!

thanks,
suresh

  reply	other threads:[~2008-07-18 22:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16 18:15 Maciej W. Rozycki
2008-07-18 10:52 ` Ingo Molnar
2008-07-18 16:25   ` Yinghai Lu
2008-07-18 17:01     ` Yinghai Lu
2008-07-18 21:03       ` Ingo Molnar
2008-07-18 21:13         ` Yinghai Lu
2008-07-18 22:02           ` Maciej W. Rozycki
2008-07-18 22:42             ` Zachary Amsden
2008-07-18 22:49               ` Suresh Siddha [this message]
2008-07-18 22:51                 ` Yinghai Lu
2008-07-18 23:00                   ` Suresh Siddha
2008-07-18 23:04                     ` Yinghai Lu
2008-07-18 23:18                       ` Suresh Siddha
2008-07-19 21:49                         ` Ingo Molnar
2008-07-19 21:53                           ` Ingo Molnar
2008-07-20 12:08                             ` Ingo Molnar
2008-07-20 15:04                               ` Ingo Molnar
2008-07-21 17:59                               ` Suresh Siddha
2008-07-22 13:24                                 ` Yong Wang
2008-07-22 13:48                                   ` Ingo Molnar
2008-07-18 23:43                 ` Zachary Amsden
2008-07-19 21:43                   ` Ingo Molnar
2008-07-18 22:58         ` Suresh Siddha
2008-07-19 21:47           ` Ingo Molnar

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=20080718224922.GB4507@linux-os.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=mingo@elte.hu \
    --cc=x86@kernel.org \
    --cc=yhlu.kernel@gmail.com \
    --cc=zach@vmware.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

Powered by JetHome