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 X-Spam-Level: X-Spam-Status: No, score=-12.7 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER, MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED, USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8541AC48BE8 for ; Mon, 14 Jun 2021 07:01:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 56042610CD for ; Mon, 14 Jun 2021 07:01:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232424AbhFNHD5 (ORCPT ); Mon, 14 Jun 2021 03:03:57 -0400 Received: from uho.ysoft.cz ([81.19.3.130]:30408 "EHLO uho.ysoft.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232096AbhFNHD5 (ORCPT ); Mon, 14 Jun 2021 03:03:57 -0400 Received: from [10.0.28.103] (unknown [10.0.28.103]) by uho.ysoft.cz (Postfix) with ESMTP id BB9E4A5525; Mon, 14 Jun 2021 09:01:52 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ysoft.com; s=20160406-ysoft-com; t=1623654112; bh=gu0pes3TKlBN2rL8ERcJGZasEHO6n0Mx/L6pFwLz0Sk=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=BDgke1fGFIU0xoSzFtYcOdxG3fnKF8Kg6AbBckoX0VfRJo/yd+yDAW68cobcy1oEe Nt++wQ9miwCi8Ni+MnU0mScSNNtFWjhHY3x2SV0a+IQ0Mxm502sfymsLDS2/yqT2hZ YzzB7nniq58uipkB+Qeu4CEOqSpVLSsP/bz/sk+w= Subject: Re: [PATCH RESEND] ARM: dts: imx6dl-yapp4: Configure the OLED display segment offset To: Shawn Guo Cc: Rob Herring , Fabio Estevam , devicetree@vger.kernel.org, Sascha Hauer , Pengutronix Kernel Team , NXP Linux Team , linux-kernel@vger.kernel.org References: <1620813314-30803-1-git-send-email-michal.vokac@ysoft.com> <20210523034952.GU8194@dragon> <9add872f-0c98-3c11-ea1f-5349f0f0bed2@ysoft.com> <20210613083512.GB29138@dragon> From: =?UTF-8?B?TWljaGFsIFZva8OhxI0=?= Message-ID: <5d1c721d-81dd-06ab-dfd1-102dbc9382e0@ysoft.com> Date: Mon, 14 Jun 2021 09:01:52 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: <20210613083512.GB29138@dragon> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 13. 06. 21 10:35, Shawn Guo wrote: > 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. > OK, fair enough, I will do so next time. Thank you for your time to explain this. Michal