From: Suzuki.Poulose@arm•com (Suzuki K. Poulose)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v5 1/8] arm64: Get rid of struct cpu_table
Date: Mon, 23 Mar 2015 17:41:42 +0000 [thread overview]
Message-ID: <55105056.4020305@arm.com> (raw)
In-Reply-To: <20150323173821.GD1556@arm.com>
On 23/03/15 17:38, Will Deacon wrote:
> On Mon, Mar 23, 2015 at 05:11:02PM +0000, Suzuki K. Poulose wrote:
>> On 18/03/15 14:55, Ard Biesheuvel wrote:
>>> @@ -209,22 +207,12 @@ static void __init smp_build_mpidr_hash(void)
>>>
>>> static void __init setup_processor(void)
>>> {
>>> - struct cpu_info *cpu_info;
>>> u64 features, block;
>>> u32 cwg;
>>> int cls;
>>>
>>> - cpu_info = lookup_processor_type(read_cpuid_id());
>>> - if (!cpu_info) {
>>> - printk("CPU configuration botched (ID %08x), unable to continue.\n",
>>> - read_cpuid_id());
>>> - while (1);
>>> - }
>>> -
>>> - cpu_name = cpu_info->cpu_name;
>>> -
>>> - printk("CPU: %s [%08x] revision %d\n",
>>> - cpu_name, read_cpuid_id(), read_cpuid_id() & 15);
>>> + printk("CPU: AArch64 Processor [%08x] revision %d\n",
>>> + read_cpuid_id(), read_cpuid_id() & 15);
>>>
>>
>> While we are at it, does it make sense to change
>>
>> s/CPU/Boot CPU/
>>
>> to make it clear on a big.Little system ?
>
> This is already queued, so I don't think it's worth the effort now.
ok, not a major one. I will fix it in one of my series
Suzuki
next prev parent reply other threads:[~2015-03-23 17:41 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 14:55 [PATCH v5 0/8] arm64: head.S cleanup Ard Biesheuvel
2015-03-18 14:55 ` [PATCH v5 1/8] arm64: Get rid of struct cpu_table Ard Biesheuvel
2015-03-18 16:11 ` Mark Rutland
2015-03-23 17:11 ` Suzuki K. Poulose
2015-03-23 17:38 ` Will Deacon
2015-03-23 17:41 ` Suzuki K. Poulose [this message]
2015-03-18 14:55 ` [PATCH v5 2/8] arm64: add macros for common adrp usages Ard Biesheuvel
2015-03-18 17:54 ` Mark Rutland
2015-03-18 17:56 ` Ard Biesheuvel
2015-03-18 18:05 ` Mark Rutland
2015-03-18 18:06 ` Ard Biesheuvel
2015-03-18 14:55 ` [PATCH v5 3/8] arm64: remove processor_id Ard Biesheuvel
2015-03-18 14:55 ` [PATCH v5 4/8] arm64: remove __switch_data object from head.S Ard Biesheuvel
2015-03-18 14:55 ` [PATCH v5 5/8] arm64: use PC-relative reference for secondary_holding_pen_release Ard Biesheuvel
2015-03-18 14:55 ` [PATCH v5 6/8] arm64: merge __enable_mmu and __turn_mmu_on Ard Biesheuvel
2015-03-18 14:55 ` [PATCH v5 7/8] arm64: remove __calc_phys_offset Ard Biesheuvel
2015-03-18 14:55 ` [PATCH v5 8/8] arm64: enforce x1|x2|x3 == 0 upon kernel entry as per boot protocol Ard Biesheuvel
2015-03-18 18:13 ` Mark Rutland
2015-03-18 18:16 ` Ard Biesheuvel
2015-03-18 18:46 ` Ard Biesheuvel
2015-03-18 18:57 ` Mark Rutland
2015-03-18 19:55 ` Ard Biesheuvel
2015-03-18 20:24 ` Mark Rutland
2015-03-19 7:30 ` Ard Biesheuvel
2015-03-19 10:35 ` Mark Rutland
2015-03-19 10:38 ` Ard Biesheuvel
2015-03-19 10:41 ` Mark Rutland
2015-03-19 11:00 ` [PATCH v3] " Ard Biesheuvel
2015-03-19 13:36 ` Mark Rutland
2015-03-20 11:31 ` Ard Biesheuvel
2015-03-20 11:41 ` Mark Rutland
2015-03-20 11:45 ` Ard Biesheuvel
2015-03-20 12:25 ` Will Deacon
2015-03-20 12:50 ` Ard Biesheuvel
2015-03-18 22:26 ` [PATCH v5 8/8] " Peter Maydell
2015-03-18 18:23 ` [PATCH v5 0/8] arm64: head.S cleanup Mark Rutland
2015-03-18 18:28 ` Ard Biesheuvel
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=55105056.4020305@arm.com \
--to=suzuki.poulose@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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