From: Dan Carpenter <error27@gmail.com>
To: Ahmet Sezgin Duran <ahmet@sezginduran.net>
Cc: gregkh@linuxfoundation.org, linux-fbdev@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] staging: sm750fb: deduplicate fbinfo loop in suspend/resume
Date: Mon, 25 May 2026 11:01:52 +0300 [thread overview]
Message-ID: <ahQB8C1gTr7LF0FO@stanley.mountain> (raw)
In-Reply-To: <20260523051509.166152-6-ahmet@sezginduran.net>
I was waiting to see if anyone had other comments bout this patchset
to decide if I should mention these minor nits. But then I was
confused about v2 so I think there might end up being comments... :P
On Sat, May 23, 2026 at 05:15:09AM +0000, Ahmet Sezgin Duran wrote:
> @@ -388,18 +388,18 @@ static int __maybe_unused lynxfb_suspend(struct device *dev)
> {
> struct fb_info *info;
> struct sm750_dev *sm750_dev;
> + int i;
>
> sm750_dev = dev_get_drvdata(dev);
>
> console_lock();
> - info = sm750_dev->fbinfo[0];
> - if (info)
> - /* 1 means do suspend */
> - fb_set_suspend(info, 1);
> - info = sm750_dev->fbinfo[1];
> - if (info)
> - /* 1 means do suspend */
> - fb_set_suspend(info, 1);
> +
> + for (i = 0; i < sm750_dev->fb_count; i++) {
> + info = sm750_dev->fbinfo[i];
> + if (info)
> + /* 1 means do suspend */
> + fb_set_suspend(info, 1);
You didn't introduce this, but the rule is the multi-line indents get
curly braces for readabilitly even if they're not required.
> + }
>
> console_unlock();
> return 0;
> @@ -414,6 +414,7 @@ static int __maybe_unused lynxfb_resume(struct device *dev)
> struct lynxfb_par *par;
> struct lynxfb_crtc *crtc;
> struct lynx_cursor *cursor;
> + int i;
>
> sm750_dev = pci_get_drvdata(pdev);
>
> @@ -421,21 +422,12 @@ static int __maybe_unused lynxfb_resume(struct device *dev)
>
> hw_sm750_inithw(sm750_dev, pdev);
>
> - info = sm750_dev->fbinfo[0];
> -
> - if (info) {
> - par = info->par;
> - crtc = &par->crtc;
> - cursor = &crtc->cursor;
> - memset_io(cursor->vstart, 0x0, cursor->size);
> - memset_io(crtc->v_screen, 0x0, crtc->vidmem_size);
> - lynxfb_ops_set_par(info);
> - fb_set_suspend(info, 0);
> - }
> + for (i = 0; i < sm750_dev->fb_count; i++) {
> + info = sm750_dev->fbinfo[i];
>
Better to delete this blank line so the NULL check is next to the
assignment.
regards,
dan carpenter
> - info = sm750_dev->fbinfo[1];
> + if (!info)
> + continue;
>
> - if (info) {
> par = info->par;
> crtc = &par->crtc;
> cursor = &crtc->cursor;
next prev parent reply other threads:[~2026-05-25 8:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 5:15 [PATCH 0/5] staging: sm750fb: various code cleanups Ahmet Sezgin Duran
2026-05-23 5:15 ` [PATCH 1/5] staging: sm750fb: remove commented-out forward declarations Ahmet Sezgin Duran
2026-05-23 5:15 ` [PATCH 2/5] staging: sm750fb: remove unnecessary initializations Ahmet Sezgin Duran
2026-05-23 5:15 ` [PATCH 3/5] staging: sm750fb: remove unused struct fields Ahmet Sezgin Duran
2026-05-23 5:15 ` [PATCH 4/5] staging: sm750fb: use ARRAY_SIZE macro in fb_find_mode loop Ahmet Sezgin Duran
2026-05-23 10:07 ` Dan Carpenter
2026-05-23 15:06 ` Ahmet Sezgin Duran
2026-05-23 16:26 ` David Laight
2026-05-23 5:15 ` [PATCH 5/5] staging: sm750fb: deduplicate fbinfo loop in suspend/resume Ahmet Sezgin Duran
2026-05-25 8:01 ` Dan Carpenter [this message]
2026-05-25 8:23 ` Ahmet Sezgin Duran
2026-05-25 16:13 ` Dan Carpenter
2026-05-25 16:31 ` Ahmet Sezgin Duran
2026-05-25 17:59 ` Dan Carpenter
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=ahQB8C1gTr7LF0FO@stanley.mountain \
--to=error27@gmail.com \
--cc=ahmet@sezginduran.net \
--cc=gregkh@linuxfoundation.org \
--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