From: Shawn Guo <shawnguo@kernel.org>
To: "Michal Vokáč" <michal.vokac@ysoft.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
devicetree@vger.kernel.org, Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] ARM: dts: imx6dl-yapp4: Configure the OLED display segment offset
Date: Sun, 13 Jun 2021 16:35:13 +0800 [thread overview]
Message-ID: <20210613083512.GB29138@dragon> (raw)
In-Reply-To: <9add872f-0c98-3c11-ea1f-5349f0f0bed2@ysoft.com>
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áč <michal.vokac@ysoft.com>
> >
> > 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
next prev parent reply other threads:[~2021-06-13 8:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 9:55 [PATCH RESEND] ARM: dts: imx6dl-yapp4: Configure the OLED display segment offset Michal Vokáč
2021-05-12 13:23 ` Fabio Estevam
2021-05-23 3:49 ` Shawn Guo
2021-05-24 8:59 ` Michal Vokáč
2021-06-13 8:35 ` Shawn Guo [this message]
2021-06-14 7:01 ` Michal Vokáč
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210613083512.GB29138@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.vokac@ysoft.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).