public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	mingo@elte.hu, tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] x86: remove unused code and data in nexgen.c
Date: Sun, 20 Apr 2008 23:45:43 +0400	[thread overview]
Message-ID: <480B9D67.7060606@gmail.com> (raw)
In-Reply-To: <480B9ADD.9060105@zytor.com>

H. Peter Anvin пишет:
> Dmitri Vorobiev wrote:
>>>
>>> Also NexGen was never shipped anyways, but bought by AMD and became
>>> the K6. So I assume whatever this file is supposed to do is done
>>> by amd.c anyways.
>>
>> IOW, you claim that now it's safe enough to throw away the NexGen
>> altogether?
>>
> 
> If it never shipped, then yes, it should be safe to remove.  We don't
> support other vendors that never went to product, e.g. RISE or Montalvo.

OK, then please drop this patch from the series (the other changes are OK,
I presume), and I'll try to take care of NexGen removal with a separate patch.

Thanks,
Dmitri

> 
>     -hpa
> 


  reply	other threads:[~2008-04-20 19:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-20  2:54 [PATCH 0/4] x86: random clean-ups Dmitri Vorobiev
2008-04-20  2:54 ` [PATCH 1/4] x86: remove unused function amd_init_cpu() Dmitri Vorobiev
2008-04-20  2:54 ` [PATCH 2/4] x86: remove unused code and data in nexgen.c Dmitri Vorobiev
2008-04-20  4:22   ` H. Peter Anvin
2008-04-20 10:33     ` [PATCH 2/2 v2] x86: remove unused function, register the cpu vendor " Dmitri Vorobiev
2008-04-20 18:51     ` [PATCH 2/4] x86: remove unused code and data " Andi Kleen
2008-04-20 19:24       ` Dmitri Vorobiev
2008-04-20 19:34         ` H. Peter Anvin
2008-04-20 19:45           ` Dmitri Vorobiev [this message]
2008-04-20 19:47             ` H. Peter Anvin
2008-04-20 20:03           ` Andi Kleen
2008-04-20 20:26             ` H. Peter Anvin
2008-04-23 18:19           ` Alan Cox
2008-04-23 19:02             ` Dmitri Vorobiev
2008-04-20  2:54 ` [PATCH 3/4] x86_64: the standard_io_resources[] array can become static Dmitri Vorobiev
2008-04-20  2:54 ` [PATCH 4/4] x86: conditionally compile sysfs stuff in intel_cacheinfo.c Dmitri Vorobiev
2008-04-21 12:25 ` [PATCH 0/4] x86: random clean-ups Ingo Molnar
     [not found]   ` <90edad820804210541h26c8e66dh70895f32e4b4038d@mail.gmail.com>
2008-04-22 14:02     ` Ingo Molnar
2008-04-22 19:18       ` Dmitri Vorobiev
2008-04-22 19:22         ` Ingo Molnar
2008-04-22 19:37           ` Dmitri Vorobiev

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=480B9D67.7060606@gmail.com \
    --to=dmitri.vorobiev@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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