From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: fbdev: Wrap user-invoked calls to fb_set_var() in helper
Date: Mon, 25 May 2026 21:30:31 +1000 [thread overview]
Message-ID: <review-patch1-20260520160744.130841-2-tzimmermann@suse.de> (raw)
In-Reply-To: <20260520160744.130841-2-tzimmermann@suse.de>
Patch Review
**Correctness**: The new `fb_set_var_from_user()` correctly consolidates the three-step pattern: check with `fbcon_modechange_possible()`, call `fb_set_var()`, then `fbcon_update_vcs()`. This is a clean factoring.
**Behavioral fix for sysfs path**: The `activate()` function in `fbsysfs.c` previously skipped `fbcon_modechange_possible()`. Now it calls it via the helper. This is a fix for an existing inconsistency, as the commit message notes — good.
**Behavioral change in sh_mobile_lcdcfb**: The original code at `sh_mobile_lcdcfb.c:1775`:
```c
var.activate = FB_ACTIVATE_NOW;
...
fbcon_update_vcs(info, true);
```
becomes (via `fb_set_var_from_user`):
```c
fbcon_update_vcs(info, var->activate & FB_ACTIVATE_ALL);
```
Since `FB_ACTIVATE_NOW` is 0 and `FB_ACTIVATE_ALL` is 64, the `all` parameter changes from `true` to `false`. This means only the current VC gets updated rather than all VCs. This may be the intended fix (the cover letter says "fix inconsistencies among the various code paths"), but it's a user-visible behavioral change that should be explicitly mentioned in the commit message.
**EXPORT_SYMBOL**: `fb_set_var_from_user` is exported with `EXPORT_SYMBOL` (not `_GPL`), matching `fb_set_var`. Fine since it's used by `ps3fb` and `sh_mobile_lcdcfb` which can be modules.
**Minor**: The removed `EXPORT_SYMBOL(fbcon_update_vcs)` and `EXPORT_SYMBOL_GPL(fbcon_modechange_possible)` in fbcon.c are now unnecessary since only fbmem.c calls them — this is correct.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-25 11:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 16:00 [PATCH 0/4] fbdev: Internalize fbcon Thomas Zimmermann
2026-05-20 16:00 ` [PATCH 1/4] fbdev: Wrap user-invoked calls to fb_set_var() in helper Thomas Zimmermann
2026-05-20 18:51 ` Helge Deller
2026-05-20 21:53 ` Christophe Leroy (CS GROUP)
2026-05-22 12:14 ` Thomas Zimmermann
2026-05-25 11:30 ` Claude Code Review Bot [this message]
2026-05-20 16:00 ` [PATCH 2/4] fbdev: Wrap user-invoked calls to fb_blank() " Thomas Zimmermann
2026-05-25 11:30 ` Claude review: " Claude Code Review Bot
2026-05-20 16:00 ` [PATCH 3/4] fbdev: Wrap fbcon updates from vga-switcheroo " Thomas Zimmermann
2026-05-20 18:49 ` Helge Deller
2026-05-25 11:30 ` Claude review: " Claude Code Review Bot
2026-05-20 16:00 ` [PATCH 4/4] fbdev: Do not export fbcon from fbdev Thomas Zimmermann
2026-05-25 11:30 ` Claude review: " Claude Code Review Bot
2026-05-25 11:30 ` Claude review: fbdev: Internalize fbcon Claude Code Review Bot
-- strict thread matches above, loose matches on Subject: below --
2026-05-22 12:28 [PATCH v2 0/4] " Thomas Zimmermann
2026-05-22 12:28 ` [PATCH v2 1/4] fbdev: Wrap user-invoked calls to fb_set_var() in helper Thomas Zimmermann
2026-05-25 8:52 ` Claude review: " Claude Code Review Bot
2026-05-27 15:14 [PATCH v3 0/4] fbdev: Internalize fbcon Thomas Zimmermann
2026-05-27 15:14 ` [PATCH v3 1/4] fbdev: Wrap user-invoked calls to fb_set_var() in helper Thomas Zimmermann
2026-05-28 2:12 ` Claude review: " Claude Code Review Bot
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=review-patch1-20260520160744.130841-2-tzimmermann@suse.de \
--to=claude-review@example.com \
--cc=dri-devel-reviews@example.com \
/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