public inbox for linux-fbdev@vger.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Helge Deller <deller@gmx.de>
Cc: Chen Ni <nichen@iscas.ac.cn>,
	linux-fbdev@vger.kernel.org,  dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 1/4] fbdev: au1100fb: Don't store device specific data in global variables
Date: Sat, 7 Feb 2026 22:34:16 +0100	[thread overview]
Message-ID: <aYevgJ6cfe6JVlJq@monoceros> (raw)
In-Reply-To: <7334e2a2-d71f-404c-b2b0-170a7117c0c5@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]

Hello Helge,

On Sat, Feb 07, 2026 at 08:04:21PM +0100, Helge Deller wrote:
> > @@ -547,7 +542,7 @@ void au1100fb_drv_remove(struct platform_device *dev)
> >   #ifdef CONFIG_PM
> >   static struct au1100fb_regs fbregs;
> 
> ^ you missed to delete "fbregs" now.
> Your previous series deleted it.

I guess this is a fallout from reordering the patches. Will fix.

> > -int au1100fb_drv_suspend(struct platform_device *dev, pm_message_t state)
> > +static int au1100fb_drv_suspend(struct platform_device *dev, pm_message_t state)
> >   {
> >   	struct au1100fb_device *fbdev = platform_get_drvdata(dev);
> > @@ -559,7 +554,7 @@ int au1100fb_drv_suspend(struct platform_device *dev, pm_message_t state)
> >   	clk_disable(fbdev->lcdclk);
> > -	memcpy(&fbregs, fbdev->regs, sizeof(struct au1100fb_regs));
> > +	memcpy(&fbdev->pm_regs, fbdev->regs, sizeof(struct au1100fb_regs));
> 
> Although memcpy() was used before, isn't this:
> 	fbdev->pm_regs = *fbdev->regs;
> sufficient and better?

Probably yes, that's a separate patch then.

Best regards
Uwe

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2026-02-07 21:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-07 17:12 [PATCH v2 0/4] fbdev: au1100fb: support COMPILE_TEST and fix multi-device support Uwe Kleine-König
2026-02-07 17:12 ` [PATCH v2 1/4] fbdev: au1100fb: Don't store device specific data in global variables Uwe Kleine-König
2026-02-07 19:04   ` Helge Deller
2026-02-07 21:34     ` Uwe Kleine-König [this message]
2026-02-08 17:48       ` Uwe Kleine-König
2026-02-07 17:12 ` [PATCH v2 2/4] fbdev: au1100fb: Mark several local functions as static Uwe Kleine-König
2026-02-07 17:12 ` [PATCH v2 3/4] fbdev: au1100fb: Use %zu to printk a value of type size_t Uwe Kleine-König
2026-02-07 19:06   ` Helge Deller
2026-02-07 21:32     ` Uwe Kleine-König
2026-02-07 17:12 ` [PATCH v2 4/4] fbdev: au1100fb: Make driver compilable on non-mips platforms Uwe Kleine-König
2026-02-07 22:02   ` kernel test robot
2026-02-07 23:04   ` kernel test robot
2026-02-08 11:12   ` kernel test robot

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=aYevgJ6cfe6JVlJq@monoceros \
    --to=u.kleine-koenig@baylibre.com \
    --cc=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=nichen@iscas.ac.cn \
    /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