From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 6B435C4332F for ; Thu, 13 Oct 2022 09:40:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=ole0R82pL+cWtT79D6nt6i/OAbkUixwnpHkBFOb8Q4I=; b=WDewGXvSQgFj6d HjwbHez4h2QXeJCLqzpLj/SzH3ZQ22/LEbJ6g3uddws8Qfh7FHns4cuRiduVo6ZlzRw5BzgIkhrgT BtfcTglx0F/bjxm8xCNW24hEPVfDgimFdAGYrkPihmHlRCbByiDBWowk25wVcXsNUbNb8BKFRslmn x6L+Z35fV9WHZ/cKPu9mw4fEkkxa97vKytjWNJn5rS0OXnV4y1nromWoSc8SUOylDdiwNmgv8s9S3 VH4uzs0pnwLjWzj0CZ2FHDahYLKAHIE9xx9odiTR6BoNv4KN6BWjZNm1OgzwwSWMWO0UccwWs5dA4 Jz9WDLLj9p2QLJ5n08lw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oiug3-00BJar-UX; Thu, 13 Oct 2022 09:38:56 +0000 Received: from mail.skyhub.de ([2a01:4f8:190:11c2::b:1457]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1oiug1-00BJZs-7V for linux-arm-kernel@lists.infradead.org; Thu, 13 Oct 2022 09:38:54 +0000 Received: from zn.tnic (p200300ea9733e733329c23fffea6a903.dip0.t-ipconnect.de [IPv6:2003:ea:9733:e733:329c:23ff:fea6:a903]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id C35B21EC053B; Thu, 13 Oct 2022 11:38:44 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1665653924; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=7sFMAuZJzUPv1j5Nd1UXqoUcoLytDTmELcFfg6XdXbI=; b=UkfI9X4nygXICvQV52k1J8hwljulApTQLTNIi7MOwkzbgsvqYYHYuYnNu+FJaG1Z3N+9rY lq2edsvl2cTGRsLoRUyhiugNuI4SUIjaHzo8Un66CpOwlEZUuauIwVoEvb/ZO2tfTdEVkb DHDvHBKrJGdhcQZybcXqlqGiRO0W078= Date: Thu, 13 Oct 2022 11:38:41 +0200 From: Borislav Petkov To: Serge Semin Cc: Serge Semin , Michal Simek , Mauro Carvalho Chehab , Tony Luck , James Morse , Robert Richter , Alexey Malahov , Michail Ivanov , Pavel Parkhomenko , Punnaiah Choudary Kalluri , Manish Narani , Dinh Nguyen , Rob Herring , Krzysztof Kozlowski , Rob Herring , Krzysztof Kozlowski , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH RESEND v3 13/17] EDAC/mc: Add MC unique index allocation procedure Message-ID: References: <20220929232712.12202-1-Sergey.Semin@baikalelectronics.ru> <20220929232712.12202-14-Sergey.Semin@baikalelectronics.ru> <20221012200154.7fq3i7igbgkcy2mx@mobilestation> <20221012223039.upbjsiywiipdrjjk@mobilestation> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20221012223039.upbjsiywiipdrjjk@mobilestation> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221013_023853_445881_DB27D3C0 X-CRM114-Status: GOOD ( 14.04 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Oct 13, 2022 at 01:30:39AM +0300, Serge Semin wrote: > A level of completeness can be relative to each person. For all the > years I've submitting the patches to the kernel I couldn't even > remember the last request to elaborate my logs. In no means I want to > say they were perfect. I could just be too immersed into the problem > so thought that the provided text was descriptive enough especially > for the subsystem maintainer. So to speak asking for more details > would be more than enough. Dude, are you even reading what I'm writing to you?! I don't care how immersed you were in the problem and who asked or didn't ask you to elaborate your logs. If you're submitting patches to the EDAC tree, those logs need to be complete and explain things sufficiently and exactly. Period. > So you need more details. You should have just asked. I can't read > your mind after all. And I can't read yours too. And I asked like three times already. And yet, you still are not giving me a concrete answer. I said "exact pointers please". That means, you point me to a driver and the *exact* *code* in there which you think is doing something which needs fixing. What you've given me again is the same spiel as before. So let me save you and me some time: your patches are not going anywhere until they explain the thing they're fixing properly and precisely. End of story. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel