Linux kernel staging patches
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ahmet Sezgin Duran <ahmet@sezginduran.net>
Cc: error27@gmail.com, linux-fbdev@vger.kernel.org,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 4/4] staging: sm750fb: deduplicate fbinfo loop in suspend/resume
Date: Tue, 7 Jul 2026 11:09:41 +0200	[thread overview]
Message-ID: <2026070721-trimming-justifier-ec8d@gregkh> (raw)
In-Reply-To: <20260525085808.171974-5-ahmet@sezginduran.net>

On Mon, May 25, 2026 at 08:58:08AM +0000, Ahmet Sezgin Duran wrote:
> lynxfb_suspend() and lynxfb_resume() both walk sm750_dev->fbinfo[]
> via duplicated per-index blocks for fbinfo[0] and fbinfo[1].
> 
> Replace each pair of blocks with a for-loop bounded by
> sm750_dev->fb_count, the number of successfully registered
> framebuffers.
> 
> No functional changes intended.

Do you have the hardware to test changes like this?


thanks,

greg k-h

  reply	other threads:[~2026-07-07  9:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-25  8:58 [PATCH v3 0/4] staging: sm750fb: various code cleanups Ahmet Sezgin Duran
2026-05-25  8:58 ` [PATCH v3 1/4] staging: sm750fb: remove commented-out forward declarations Ahmet Sezgin Duran
2026-05-25  8:58 ` [PATCH v3 2/4] staging: sm750fb: remove unnecessary initializations Ahmet Sezgin Duran
2026-05-25  8:58 ` [PATCH v3 3/4] staging: sm750fb: remove unused struct fields Ahmet Sezgin Duran
2026-05-25  8:58 ` [PATCH v3 4/4] staging: sm750fb: deduplicate fbinfo loop in suspend/resume Ahmet Sezgin Duran
2026-07-07  9:09   ` Greg KH [this message]
2026-07-07 11:49     ` Ahmet Sezgin Duran
2026-07-07 12:27       ` Ahmet Sezgin Duran

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=2026070721-trimming-justifier-ec8d@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=ahmet@sezginduran.net \
    --cc=error27@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@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