From: Michal Gorlas <michal.gorlas@9elements.com>
To: Brian Norris <briannorris@chromium.org>
Cc: Tzung-Bi Shih <tzungbi@kernel.org>,
Julius Werner <jwerner@chromium.org>,
marcello.bauer@9elements.com, chrome-platform@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/3] firmware: coreboot: support for parsing SMM related informations from coreboot tables
Date: Tue, 17 Jun 2025 11:37:17 +0200 [thread overview]
Message-ID: <aFE3TVxqpt4-lmYP@cyber-t14sg4> (raw)
In-Reply-To: <aFBfcg7E38ywGD5W@google.com>
On Mon, Jun 16, 2025 at 11:16:18AM -0700, Brian Norris wrote:
> On Sat, Jun 14, 2025 at 02:53:18PM +0200, Michal Gorlas wrote:
> > On Thu, Jun 12, 2025 at 03:37:40PM -0700, Brian Norris wrote:
> > > > @@ -112,8 +122,8 @@ void coreboot_driver_unregister(struct coreboot_driver *driver);
> > > > * boilerplate. Each module may only use this macro once, and
> > > > * calling it replaces module_init() and module_exit()
> > > > */
> > > > -#define module_coreboot_driver(__coreboot_driver) \
> > > > +#define module_coreboot_driver(__coreboot_driver) \
> > > > module_driver(__coreboot_driver, coreboot_driver_register, \
> > > > - coreboot_driver_unregister)
> > > > + coreboot_driver_unregister)
> > >
> > > You're making arbitrary whitespace changes in this hunk. Try to avoid
> > > that, please.
> > >
> >
> > Sure, will do. It came from a style warning when running
> > scripts/checkpatch.pl. I thought it could be useful to fix it on the
> > same go.
>
> That's odd, I don't see any such warning. Anyway, typically I'd expect
> such things not to be lumped together under the "separate your changes"
> guidance of Documentation/process/submitting-patches.rst (if they're
> worth changing at all), although that may not be a hard and fast rule.
My bad, the whitespace were not a consequence of checkpatch.pl
complaints, but rather running clang-format on coreboot_table.h
on a clean tree:
* $ clang-format -i drivers/firmware/google/coreboot_table.h
* $ git diff
* diff --git a/drivers/firmware/google/coreboot_table.h b/drivers/firmware/google/coreboot_table.h
* index bb6f0f7299b4..3d933c657535 100644
* --- a/drivers/firmware/google/coreboot_table.h
* +++ b/drivers/firmware/google/coreboot_table.h
* @@ -61,15 +61,15 @@ struct lb_framebuffer {
* u32 x_resolution;
* u32 y_resolution;
* u32 bytes_per_line;
* - u8 bits_per_pixel;
* - u8 red_mask_pos;
* - u8 red_mask_size;
* - u8 green_mask_pos;
* - u8 green_mask_size;
* - u8 blue_mask_pos;
* - u8 blue_mask_size;
* - u8 reserved_mask_pos;
* - u8 reserved_mask_size;
* + u8 bits_per_pixel;
* + u8 red_mask_pos;
* + u8 red_mask_size;
* + u8 green_mask_pos;
* + u8 green_mask_size;
* + u8 blue_mask_pos;
* + u8 blue_mask_size;
* + u8 reserved_mask_pos;
* + u8 reserved_mask_size;
* };
*
* /* A device, additionally with information from coreboot. */
* @@ -112,8 +112,8 @@ void coreboot_driver_unregister(struct coreboot_driver *driver);
* * boilerplate. Each module may only use this macro once, and
* * calling it replaces module_init() and module_exit()
* */
* -#define module_coreboot_driver(__coreboot_driver) \
* +#define module_coreboot_driver(__coreboot_driver) \
* module_driver(__coreboot_driver, coreboot_driver_register, \
* - coreboot_driver_unregister)
* + coreboot_driver_unregister)
*
* #endif /* __COREBOOT_TABLE_H */
Anyway, I am not sure if it is even worth changing, its rather cosmetic. I
removed these changes in v2.
Best,
Michal
next prev parent reply other threads:[~2025-06-17 9:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 14:05 [PATCH v1 0/3] firmware: coreboot: Support for System Management Interrupt (SMI) handling in coreboot payload (MM payload concept) Michal Gorlas
2025-06-12 14:05 ` [PATCH v1 1/3] firmware: coreboot: support for parsing SMM related informations from coreboot tables Michal Gorlas
2025-06-12 22:37 ` Brian Norris
2025-06-14 12:53 ` Michal Gorlas
2025-06-16 18:16 ` Brian Norris
2025-06-17 9:37 ` Michal Gorlas [this message]
2025-06-12 14:05 ` [PATCH v1 2/3] firmware: coreboot: loader for Linux-owned SMI handler Michal Gorlas
2025-06-12 22:38 ` Brian Norris
2025-06-14 12:59 ` Michal Gorlas
2025-06-16 18:07 ` Brian Norris
2025-06-17 11:39 ` Michal Gorlas
2025-06-13 5:21 ` kernel test robot
2025-06-12 14:05 ` [PATCH v1 3/3] firmware: coreboot: Linux-owned SMI handler to be loaded by coreboot Michal Gorlas
2025-06-12 22:38 ` Brian Norris
2025-06-13 12:11 ` 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=aFE3TVxqpt4-lmYP@cyber-t14sg4 \
--to=michal.gorlas@9elements.com \
--cc=briannorris@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=jwerner@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcello.bauer@9elements.com \
--cc=tzungbi@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