Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp403827imm; Thu, 6 Sep 2018 04:28:52 -0700 (PDT) X-Google-Smtp-Source: ANB0VdZfPqwYphSHKqMVl29QN0B55+BG7dyU+/boKHKyKk+5+mTPbgzYg32rUtqw+ol9NJOEh8/h X-Received: by 2002:a62:4898:: with SMTP id q24-v6mr2388957pfi.22.1536233332835; Thu, 06 Sep 2018 04:28:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536233332; cv=none; d=google.com; s=arc-20160816; b=vNwmaBRy19yiUaio9Wnnj297lff5cIFTmZrcFhDOS0300lj3K0Xbdf6s5wPQI6q+Xo rU6ruC6+QG1xK3BvAg0/hoV31f5PZuFdjGy48QfwdowO+9pqSU9xcyzJZFaYQCvPLYhO FnmlfhvTfj68aPkC9/LZ5dtDSXuY07KzzRJQIDR1bC/0vL8I3ys8gHf8zET7mVUCmoRR gcLTQrABEk2CDjqW5FvfVbpFLkTXL6jQuVumBPgbIXSQTojJQWL+IIRVG2RGM6cq7BBT /i0nGsm0Z6Enmnk31CKnbTlrEM+zvoToyAiA3MItJLS6d3cMJJoz9+5UUWHvCxE2G9OD fxQA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=flz+0719QiJsdJbk83y9AaUb8jRz8QeOKqh6ieJYj6Y=; b=dAVaX/iZAAhSwy3aaBC/sILxAeIZ7jGorkMRKfWEIKDyYFtmtwAm9gXsoXl+bBomSv 5/U6vJ+M24KhPrC7AwF+P0xiGVlXHGL6dAOz8Tan00zSwSWG7MQWLhOCeu4pG0zC6h3v bNkNMlnsDAE5SNubJOC0/eBxn7ks//B3oOi3edNqSZUzyjSDURHhrrpY3mrWk/1uATGg pqSEjPhG1RmCEUniPYe3X3p6tiEM/K7h+SeBjFjZnwm+PzZ73nCtBQ7DIjaC8hwBCBJ9 OwcnPcyBjYOAQVb6MNTuIor3aE3zxylJChUkNyk6S3QqCHUC3m3Qg6Be+qCArvNNOdeT Cs+A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=d915Tg8r; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i135-v6si4918891pgc.154.2018.09.06.04.28.35; Thu, 06 Sep 2018 04:28:52 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=d915Tg8r; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728521AbeIFPsB (ORCPT + 99 others); Thu, 6 Sep 2018 11:48:01 -0400 Received: from mail.kernel.org ([198.145.29.99]:46116 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727665AbeIFPsB (ORCPT ); Thu, 6 Sep 2018 11:48:01 -0400 Received: from mail-qt0-f169.google.com (mail-qt0-f169.google.com [209.85.216.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 3D55D20857; Thu, 6 Sep 2018 11:13:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1536232384; bh=flz+0719QiJsdJbk83y9AaUb8jRz8QeOKqh6ieJYj6Y=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=d915Tg8rkJVzxdJkiYphVOW4p00aBMLQzvcJNeXwqjmVlSd2UUduPfDoH1A71nHDg 4PT+X/RoEIa6tHlbbJT14M7wudnCYqWaNvcSXQR4jgLA34BOv1SejcSUW5ZcTWborZ h8Wn4uDl36F/AVaULKzUm+fQj8CotH5RO+AJ3fQA= Received: by mail-qt0-f169.google.com with SMTP id x7-v6so11713147qtk.5; Thu, 06 Sep 2018 04:13:04 -0700 (PDT) X-Gm-Message-State: APzg51AsbBY2BwNPIZnXnP8R7cPLVA9StMDR35H6c6M0ChfBYn6EeDFt sMn5uczZvHT8SXJK1RFW6IaqlEVjY2GyezyK0w== X-Received: by 2002:aed:2aa1:: with SMTP id t30-v6mr1576509qtd.101.1536232383452; Thu, 06 Sep 2018 04:13:03 -0700 (PDT) MIME-Version: 1.0 References: <20180905193738.19325-1-robh@kernel.org> <20180905193738.19325-19-robh@kernel.org> <20180906083506.GA10768@zn.tnic> In-Reply-To: <20180906083506.GA10768@zn.tnic> From: Rob Herring Date: Thu, 6 Sep 2018 06:12:51 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 18/21] edac: cpc925: use for_each_of_cpu_node iterator To: Borislav Petkov Cc: devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" , Mauro Carvalho Chehab , linux-edac@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Sep 6, 2018 at 3:35 AM Borislav Petkov wrote: > > On Wed, Sep 05, 2018 at 02:37:35PM -0500, Rob Herring wrote: > > Use the for_each_of_cpu_node iterator to iterate over cpu nodes. This > > has the side effect of defaulting to iterating using "cpu" node names in > > preference to the deprecated (for FDT) device_type == "cpu". > > > > Cc: Borislav Petkov > > Cc: Mauro Carvalho Chehab > > Cc: linux-edac@vger.kernel.org > > Signed-off-by: Rob Herring > > --- > > Please ack and I will take via the DT tree. This is dependent on the > > first 2 patches. > > Completely unknown territory for me so I'd trust your judgement. Staring > at 1/21, the conversion looks ok except the removal of those prints that > a cpu nodes are not present - I wonder if they even meant anything or > were just there during driver development... I should have noted this. It's not the kernel's job to validate the DT and certainly not some driver's job to validate cpu nodes. It's bad enough that some random driver is parsing cpu nodes. If they are missing or are crap, you should get warnings or messages well before this point. Rob