Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp265522ybh; Wed, 11 Mar 2020 00:26:26 -0700 (PDT) X-Google-Smtp-Source: ADFU+vvdL+KRiN5dO5TdwU6RW5l1VNtiALexeJSMUJdKBNSX30i12CqJIMjw105e91FiSoV5+F6t X-Received: by 2002:a9d:7085:: with SMTP id l5mr1225559otj.53.1583911586411; Wed, 11 Mar 2020 00:26:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1583911586; cv=none; d=google.com; s=arc-20160816; b=nzHdKvEdssDH0FJKAdm7kMGKFfkET8T21yuT22KOuHK3VEXztqmfPgvFQBveJZMMvr 1o2DBW1f8jxZFzyqgzeu3CNk1lpOnUWDe3oFjym5/6P6JUIoEJZ5FOwtvILuLYvDtX8F wRSS6Tx+MztmMZ2yOUMQwQvvmJRAdF7GwQEIn6RdYM/ZfTlXmJAJ+hlrOky9cwNL1jqx e5D6LkAHdzYy6ebZFtYEa91r6b43IQM47ZmxYTTCUmLeZ2HL0oEaoW04NIqkZ6ifHmpN LEm5GQmg7wLBg0yL/1Fz/Zz9D+9AMoyaeNmeuFsIC6fO7P7iW/Q7ki6rNm/DCx2er/RZ Hu7g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=wqYs6HWBa+0jE5lRFRcrzRMWgNG3cQgv96yBXEDGaWY=; b=fLI0nobkEQFQFYvaRQ7K8tmHk8Gd+/sBPbRN3S8FEAUJD/AU6fBdDgUQNyxmSGrBHK vuy42xAz2FoPg+r6rPPuZynv9ZkscnR4bb5vz0EXHZ5xj50/brHolMrwp3XTiNQIqnbk qB6C80a0cdBSej+Ee5raEyDuz6N2zVW4DjKxgNuMDqR5NLFzQCSiadI1MxrkUrZYg9N/ zHVdjdHopJpXX0e0WeCtYjhf6lkJu6DpqwHshMqwCmSeuwqsxh8tLa+azGVh1VS4X7qC fG4OQ/3A4Iqrhkw/wJ1h1fVU36Lf++pnMSijGryAiip/XFhiEeLbLuiv1mD3yQFHCHKN 3Zww== ARC-Authentication-Results: i=1; mx.google.com; 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 v10si588746ote.45.2020.03.11.00.26.14; Wed, 11 Mar 2020 00:26:26 -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; 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 S1728443AbgCKHZ2 convert rfc822-to-8bit (ORCPT + 99 others); Wed, 11 Mar 2020 03:25:28 -0400 Received: from relay11.mail.gandi.net ([217.70.178.231]:43931 "EHLO relay11.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726672AbgCKHZ1 (ORCPT ); Wed, 11 Mar 2020 03:25:27 -0400 Received: from xps13 (lfbn-tou-1-1473-158.w90-89.abo.wanadoo.fr [90.89.41.158]) (Authenticated sender: miquel.raynal@bootlin.com) by relay11.mail.gandi.net (Postfix) with ESMTPSA id DA407100006; Wed, 11 Mar 2020 07:25:23 +0000 (UTC) Date: Wed, 11 Mar 2020 08:25:22 +0100 From: Miquel Raynal To: masonccyang@mxic.com.tw Cc: "Boris Brezillon" , allison@lohutok.net, bbrezillon@kernel.org, frieder.schrempf@kontron.de, juliensu@mxic.com.tw, linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org, rfontana@redhat.com, richard@nod.at, s.hauer@pengutronix.de, stefan@agner.ch, tglx@linutronix.de, vigneshr@ti.com, yuehaibing@huawei.com Subject: Re: [PATCH v3 1/4] mtd: rawnand: Add support manufacturer specific lock/unlock operation Message-ID: <20200311082522.53313163@xps13> In-Reply-To: References: <1583220084-10890-1-git-send-email-masonccyang@mxic.com.tw> <1583220084-10890-2-git-send-email-masonccyang@mxic.com.tw> <20200310202723.16b48f4b@collabora.com> Organization: Bootlin X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Mason, Boris, masonccyang@mxic.com.tw wrote on Wed, 11 Mar 2020 10:40:04 +0800: > Hi Boris, > > > > Add nand_lock() & nand_unlock() for manufacturer specific lock & > unlock > > > operation while the device supports Block Portection function. > > > > > > Signed-off-by: Mason Yang > > > Reported-by: kbuild test robot > > > > Reported-by on something that's not a fix doesn't make sense. I know > > the 0day bot asked you to add this tag, but that should only be done if > > you submit a separate patch, ideally with a Fixes tag. If the offending > > patch has not been merged yet, you should just fix the commit and ignore > > the Reported-by tag (you can mention who reported the problem in the > > changelog though). Yesterday when applying all the NAND patches my personal IP address got flagged as spam by mistake (~500 mails in ~10s) so I could not answer manually as I wished. Indeed, this Reported-by tag was not needed and I dropped it manually when applying. This tag is meant to show an error that was existing *before* your series and that you are fixing with your series. This is not something you should add when a robot tells you something is wrong in your series. Also, I rewrote several paragraphs and I prefixed two of them with "mtd: rawnand: macronix:". Thanks, Miquèl