Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp1887792pxj; Sun, 13 Jun 2021 01:37:08 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyRqmrLgumoMj27JuwoG4v/9Il+isa2OgIUbXE1ltio54UcVn8948AzKlIhkk2WLt2UDU4z X-Received: by 2002:a17:906:268c:: with SMTP id t12mr10508177ejc.441.1623573428082; Sun, 13 Jun 2021 01:37:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623573428; cv=none; d=google.com; s=arc-20160816; b=0OBBoCoy1Kxy6TADHxMjre8cgB1WFqfglEat7DuA5eeKTkYdjVo1BVsVAqD2o1amOG 7bpgXHIjnUcNZpqhQKnjGTgCIk94WKbTfhiY0BGv/lS6s46HPBXt/Y6s4ygU6BM1YtoU 9Qd8RaBeaXXZcvxmN2BpLXqjOT5kjozc4QEHgbk5fD5YPLK79AUsZreFTkublzLvZoTR bLFQB/cld82iHo+ux2RXWwfBMvvDH/teE+JOh5ol59ffBDUcELts7u2noNZ+GidXjXwu m/4mirBCzTtbW0vjX19O5Khqtaa2zQY/Z8eJ2FfKMpHi1Oxs0BYs22vxLzB7W23dJajC /o+g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=xjsT+s8emK8t4eAOu7t1Hya66y2/09QsObLzDvy0eyc=; b=LgbKrGvPPWD+4yw1vWaVuEx+4Wx98xg4uOs49Ruv0rFI5n/IpXlHobyAwyLKgvNkbG tkT9R0X3s7jnIdZpseLlV0ZUguR8Gt62kMkFZe2D9WfPWHCZbF4g73fcWqyDbsv5XYQm 3LB8oXfXrJPT/N41CkSPwPmgRZ1EGC5B7EhUwtS+mXTSIXkwb5vpnioVrfqRdb59qj8t YQRHMnnl6H7ZHrr8N/5zy3F2Ur616jBtOd4RjqredaDuCS649rZqcwZ1V2TRKaVb7/Nq BaYlHBSUyqEVdk5yKffw2dNwGV4NQVhAWY8yxV7A9zwy1nP5aIsi0Hx+229ioccJFcDl p6Bg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=YVKlEj8r; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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. [23.128.96.18]) by mx.google.com with ESMTP id b19si6822136ede.547.2021.06.13.01.36.45; Sun, 13 Jun 2021 01:37:08 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=YVKlEj8r; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 S231286AbhFMIhT (ORCPT + 99 others); Sun, 13 Jun 2021 04:37:19 -0400 Received: from mail.kernel.org ([198.145.29.99]:49134 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230435AbhFMIhT (ORCPT ); Sun, 13 Jun 2021 04:37:19 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id DC0E2610A0; Sun, 13 Jun 2021 08:35:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1623573318; bh=u+5RuXoIpdCPzSoPH35t+Q5SAfW+Qhc58p3O+tzvhgk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=YVKlEj8rYrwCCFq/4XZLDESTM9Rx1wz1F3sS89Ch1gurR3mh1UkqiN51z0eyA1KeQ kOMujjfizroSAeZre6C6iJEiXPre8ZPhL1JexJTYJ8dEVGTpmUz7LMTZHtYiMoPxSV IhDPhYD4C4PhXHLbikofNwi+qYQXpWHOgZI9WwryH8kPxjHEvEYyaTy+VzKVZoUq3X y5ZhLYmvHCvrdkfoTih1FvuwQOygd/ETl+4OKy9BR7JWcVF+ERgHxsw9QDhVBVZrjj 3Z6saNo/m5d6asGpUEMsrode+UbtIVyL6AaR273hJjGZexwWbx2q9qY2xkTjiW8Lm4 akXMULgcSJ2ig== Date: Sun, 13 Jun 2021 16:35:13 +0800 From: Shawn Guo To: Michal =?utf-8?B?Vm9rw6HEjQ==?= Cc: Rob Herring , Fabio Estevam , devicetree@vger.kernel.org, Sascha Hauer , Pengutronix Kernel Team , NXP Linux Team , linux-kernel@vger.kernel.org Subject: Re: [PATCH RESEND] ARM: dts: imx6dl-yapp4: Configure the OLED display segment offset Message-ID: <20210613083512.GB29138@dragon> References: <1620813314-30803-1-git-send-email-michal.vokac@ysoft.com> <20210523034952.GU8194@dragon> <9add872f-0c98-3c11-ea1f-5349f0f0bed2@ysoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <9add872f-0c98-3c11-ea1f-5349f0f0bed2@ysoft.com> User-Agent: Mutt/1.9.4 (2018-02-28) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 24, 2021 at 10:59:14AM +0200, Michal Vokáč wrote: > On 23. 05. 21 5:49, Shawn Guo wrote: > > On Wed, May 12, 2021 at 11:55:14AM +0200, Michal Vokáč wrote: > > > The imx6dl-yapp4 platform uses a GE-LX012864FWPP3N0000 OLED display. > > > The display consist of a 128x64 OLED panel and a SSD1305 controller. > > > > > > The OLED panel resolution is 128x64 but the built-in controller default > > > resolution is 132x64. To display properly a segment offset needs to be > > > configured. > > > > > > Signed-off-by: Michal Vokáč > > > > Why are you resending? Please state reason when you resend. > > I can't tell where but a while ago I read in some documentation > that if you do not get any response for aprox. two weeks you > can/should resend the patch in case it fell through the cracks. > I sent these patches in the middle of April, four weeks ago, > and have got no replies since then. So I [RESEND PATCH] these. No. You can send a ping if there is no response for 2~3 weeks but not RESEND. RESEND is normally used to refresh aged patches that needs to be rebased to the latest release, or to make some minor update that doesn't deserve a new version, like error in commit log etc. > > I totally understand that you, and all maintainers and reviewers > in general, are very busy so it may take a long time to reply. > > AFAIK one does not need to state a reason for RESEND PATCH. > The word RESEND itself should explain the reason. This is not v2, > where I would of course describe what has changed. No. Always state the reason for resending. Maintainers do not know why you are resending. Shawn > > Please correct me if my understanding of this part of the submitting > process is incorrect. > > Thank you, > Michal