Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp6075145ybc; Wed, 27 Nov 2019 14:35:50 -0800 (PST) X-Google-Smtp-Source: APXvYqwYcv3nvE/v8v636Y6PhZYRI5Q9rdAvBxTF3M67H46YBEzzLU14Ko6h01h51SESBhUq/bFX X-Received: by 2002:a17:906:9482:: with SMTP id t2mr35011475ejx.38.1574894150222; Wed, 27 Nov 2019 14:35:50 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574894150; cv=none; d=google.com; s=arc-20160816; b=NgBPKpyhXErsWivDRBWhP4leRYgL1TD7OQlA3xLro+165Dj5jJ4CniwG2IRvaBcqk7 5Ut9C08iE9CgyFlgvgYaVqP336s7NrH3KoyjynzP5Mkxcc+Ni+WBk1io8tbA7Gr93Lpd 4wVrvX3b1g1URw1UskiFNl9U7edfZJA6ZPmlnJzaKqHaoYy5dZzoadlVZntefCMWsNFn 1jPuNmjf/ZbX1JslLisq3tP36TgHw1dTSZWtq72jB5/8UdZgp1vxWvPQ3xlCV9fbakiJ USQgFFqboJX/Gg4Op2Ga+sk0qRDs5lOB/zmHB+wJTm5horu6w2oI3wYjXiKsdTd9h6FK fAqQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:subject:cc:to:from:date:references :in-reply-to:message-id:mime-version:user-agent:dkim-signature :dkim-signature; bh=IzkBKtsIWNt/0KHfahdEn8h/zDvhTn2y2qgOjDS+X54=; b=Hyxi6VS8ktvb4beZMLjPZ/348ZMmNC63usbw1HGWVDsOvASeiQl6jrnCQnWRt8cyIx GVcesmeIepKWGUrJaTUaLLOGA2uDZbaYr7iyGnfyqXrnunHMqqYBtaD04auzhOObr/c5 K7beNrM6Snxu5uG0L3qr3Crzc+sNrqt/Q7oYkCAOKzyy49tILcbgaR6X5isd7OS2QciL iCE7OVefQkQ2nDenKYgBDOc0sS1a15Sk487n6sCXBNDwa7uFwegQExkrBKl45kCGXBtg lan5YkBn8/fIDSNj4A1AWytpagyjc7HiHanhKqn+NA08I1TgRjBGhZiypIghRGVW/qOJ 9Egg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@aj.id.au header.s=fm1 header.b=JyfZhtH6; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=CkWluTh8; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h2si10186991ejt.8.2019.11.27.14.35.25; Wed, 27 Nov 2019 14:35:50 -0800 (PST) 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=@aj.id.au header.s=fm1 header.b=JyfZhtH6; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=CkWluTh8; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727318AbfK0Wdy (ORCPT + 99 others); Wed, 27 Nov 2019 17:33:54 -0500 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:41781 "EHLO out5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726947AbfK0Wdx (ORCPT ); Wed, 27 Nov 2019 17:33:53 -0500 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 32353226DF; Wed, 27 Nov 2019 17:33:52 -0500 (EST) Received: from imap2 ([10.202.2.52]) by compute4.internal (MEProxy); Wed, 27 Nov 2019 17:33:52 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aj.id.au; h= mime-version:message-id:in-reply-to:references:date:from:to:cc :subject:content-type; s=fm1; bh=IzkBKtsIWNt/0KHfahdEn8h/zDvhTn2 y2qgOjDS+X54=; b=JyfZhtH6I0ZKd2o2M57TsCUen61dfpyhBJHt1MIXtLQoq+m +2SV44eMSwO3/Sg3qCJSQzC9ivUtSYXsGmQPjJx1x92rJGsl7jg4F3Q5kkIqS/3Q TeMYsnZJix15P8V/a/Q704xp6FdQdOwNkTmacY8XgVnOU0z0YplSIS1yS/31rJLU FD2hdDpUnu37PYM9byWslm84bFryGXoRbHA3XgHg0pnQn4YiXchz+H9KCI4BhHKX S1MSNRCgJuzAyk/rq0SKAb7PHdCh2TaV8QgqOc/izm/fljxM23UEQYh6VAAYFCou cXe2zHFlCv63fYqIRSutrZI9lcymfM820VwNejQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=IzkBKt sIWNt/0KHfahdEn8h/zDvhTn2y2qgOjDS+X54=; b=CkWluTh8Tm5dT5epjP51lz jx5K+LxQqnCvdtEo+rOmMggbUljcIaeSvt4GZrpi/CBMMN2fQpfnar53Sl4FC8ab 62BiZNuRSczkqqqKfOTf+pQfwmnlrf0eF7isYQijN+JU1G/PTE2IUIBhpzKeme0K a4SYsLk2pofV41p9vwvlbfz9taVYkkHsQhb4+F27+NBG1QKivNfw+B2fXW5a67RF 0q4ZB1acSoXDf2Xbas7pyFvq1KGNPmBlJV8CRY6y2aLvNhAVW4TaQk+/rhSKwOdM W9njISK6GvSGBakXljoJHbW55s7/ISiNUc2ohS8LlolIEkGfbxCCW3sfesUeimWg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudeihedgudeiudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefofgggkfgjfhffhffvufgtsehttdertderredtnecuhfhrohhmpedftehn ughrvgifucflvghffhgvrhihfdcuoegrnhgurhgvfiesrghjrdhiugdrrghuqeenucfrrg hrrghmpehmrghilhhfrhhomheprghnughrvgifsegrjhdrihgurdgruhenucevlhhushht vghrufhiiigvpedt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 3D649E00A3; Wed, 27 Nov 2019 17:33:51 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.7-578-g826f590-fmstable-20191119v1 Mime-Version: 1.0 Message-Id: In-Reply-To: <20191127132340.GA22672@cnn> References: <20191127132340.GA22672@cnn> Date: Thu, 28 Nov 2019 09:05:21 +1030 From: "Andrew Jeffery" To: manikandan-e Cc: "Joel Stanley" , "Sai Dasari" , "Vijay Khemka" , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-aspeed@lists.ozlabs.org, manikandan.e@hcl.com Subject: Re: [PATCH v4] ARM: dts: aspeed: Adding Facebook Yosemite V2 BMC Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 27 Nov 2019, at 23:53, manikandan-e wrote: > The Yosemite V2 is a facebook multi-node server > platform that host four OCP server. The BMC > in the Yosemite V2 platorm based on AST2500 SoC. > > This patch adds linux device tree entry related to > Yosemite V2 specific devices connected to BMC SoC. > > Signed-off-by: manikandan-e If people have reviewed previous versions of your patches and sent Reviewed-by/Acked-by/Tested-by tags, please make sure to include them on future versions of the patches _unless_ there has been significant change that might invalidate the tag. In that case, also provide a short description as to why you dropped the tags. You can add free-form information below the `---` and it will not be included in the commit for the patch. Cheers, Andrew