From: Sui Jingfeng <15330273260@189.cn>
To: Javier Martinez Canillas <javierm@redhat.com>,
linux-kernel@vger.kernel.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: drm/ssd130x: Fix include guard name
Date: Sat, 13 May 2023 21:29:46 +0800 [thread overview]
Message-ID: <ab3a2467-2236-604f-b4aa-862a7ac838e9@189.cn> (raw)
In-Reply-To: <20230512120232.304603-1-javierm@redhat.com>
Reviewed-by: Sui Jingfeng <suijingfeng@loongson.cn>
On 2023/5/12 20:02, Javier Martinez Canillas wrote:
> This is a leftover from an early iteration of the driver when it was still
> named ssd1307 instead of ssd130x. Change it for consistency with the rest.
>
> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
> Reviewed-by: Sam Ravnborg <sam@ravnborg.org>
> ---
>
> drivers/gpu/drm/solomon/ssd130x.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/solomon/ssd130x.h b/drivers/gpu/drm/solomon/ssd130x.h
> index 03038c1b6476..db03ee5db392 100644
> --- a/drivers/gpu/drm/solomon/ssd130x.h
> +++ b/drivers/gpu/drm/solomon/ssd130x.h
> @@ -10,8 +10,8 @@
> * Copyright 2012 Free Electrons
> */
>
> -#ifndef __SSD1307X_H__
> -#define __SSD1307X_H__
> +#ifndef __SSD130X_H__
> +#define __SSD130X_H__
>
> #include <drm/drm_connector.h>
> #include <drm/drm_crtc.h>
> @@ -94,4 +94,4 @@ struct ssd130x_device *ssd130x_probe(struct device *dev, struct regmap *regmap);
> void ssd130x_remove(struct ssd130x_device *ssd130x);
> void ssd130x_shutdown(struct ssd130x_device *ssd130x);
>
> -#endif /* __SSD1307X_H__ */
> +#endif /* __SSD130X_H__ */
next prev parent reply other threads:[~2023-05-13 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 12:02 [PATCH] " Javier Martinez Canillas
2023-05-12 13:42 ` Sam Ravnborg
2023-05-13 13:29 ` Sui Jingfeng [this message]
2023-05-15 12:09 ` Javier Martinez Canillas
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=ab3a2467-2236-604f-b4aa-862a7ac838e9@189.cn \
--to=15330273260@189.cn \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®