From: Raag Jadav <raag.jadav@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Helge Deller <deller@gmx.de>,
Thorsten Blum <thorsten.blum@linux.dev>,
Chelsy Ratnawat <chelsyratnawat2001@gmail.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fbdev/pxafb: Fix multiple clamped values in pxafb_adjust_timing
Date: Wed, 3 Dec 2025 11:30:36 +0100 [thread overview]
Message-ID: <aTARTP6VhZG7-JEf@black.igk.intel.com> (raw)
In-Reply-To: <aTAHkxg1_LDzZNSb@smile.fi.intel.com>
On Wed, Dec 03, 2025 at 11:49:07AM +0200, Andy Shevchenko wrote:
> On Tue, Dec 02, 2025 at 08:36:08PM +0100, Helge Deller wrote:
> > On 12/2/25 19:36, Thorsten Blum wrote:
> > > On 2. Dec 2025, at 19:28, Helge Deller wrote:
> > > > On 12/2/25 19:15, Thorsten Blum wrote:
>
> ...
>
> > > > How did you notice? Do you actually have the hardware and tested it?
> > >
> > > I only compile-tested it.
> > >
> > > I stumbled upon another driver with the same bug and then used grep to
> > > search for other instances and found about 6 or 7, including this one.
> >
> > Ok. But this then means, maybe the clamping isn't needed (since nobody complained),
> > or that nobody noticed because nobody uses the driver any longer.
>
> I think it's a combination of factors: 1) rarely people have this hardware,
> especially nowadays, to run more or less new kernel; 2) there are no conditions
> happened that this patch fixes in their environments; 3) something else I
> missed.
I had a quick look at commit 3f16ff608a75 and seems like there wasn't much
happening either way.
Raag
next prev parent reply other threads:[~2025-12-03 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 18:15 [PATCH] fbdev/pxafb: Fix multiple clamped values in pxafb_adjust_timing Thorsten Blum
2025-12-02 18:28 ` Helge Deller
2025-12-02 18:36 ` Thorsten Blum
2025-12-02 19:36 ` Helge Deller
2025-12-03 9:49 ` Andy Shevchenko
2025-12-03 10:30 ` Raag Jadav [this message]
2025-12-02 20:32 ` David Laight
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=aTARTP6VhZG7-JEf@black.igk.intel.com \
--to=raag.jadav@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=chelsyratnawat2001@gmail.com \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thorsten.blum@linux.dev \
--cc=tzimmermann@suse.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