From: Nam Cao <namcao@linutronix.de>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: ChanSoo Shin <csshin9928@gmail.com>,
andy@kernel.org, gregkh@linuxfoundation.org,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-staging@lists.linux.dev
Subject: Re: [PATCH v5] fbtft: limit dirty rows based on damage range
Date: Fri, 06 Feb 2026 17:51:45 +0700 [thread overview]
Message-ID: <87ms1mb0vy.fsf@yellow.woof> (raw)
In-Reply-To: <aYXEHajVeKvIMmL7@smile.fi.intel.com>
Andy Shevchenko <andriy.shevchenko@intel.com> writes:
> Do you have an actual HW to test? If not, won't be applied either.
Yes, a pair with SPI interface.
Nam
next prev parent reply other threads:[~2026-02-06 10:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 20:39 [PATCH v5] fbtft: limit dirty rows based on damage range ChanSoo Shin
2026-01-28 22:35 ` Andy Shevchenko
2026-01-29 6:29 ` Dan Carpenter
2026-01-29 10:59 ` Andy Shevchenko
2026-02-06 0:04 ` Nam Cao
2026-02-06 10:36 ` Andy Shevchenko
2026-02-06 10:51 ` Nam Cao [this message]
2026-02-06 11:35 ` Andy Shevchenko
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=87ms1mb0vy.fsf@yellow.woof \
--to=namcao@linutronix.de \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=csshin9928@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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