From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>, Nikita Kravets <teackot@gmail.com>
Cc: platform-driver-x86@vger.kernel.org,
Aakash Singh <mail@singhaakash.dev>,
Jose Angel Pastrana <japp0005@red.ujaen.es>
Subject: Re: [PATCH v2 3/3] platform/x86: msi-ec: Add more EC configs
Date: Mon, 9 Oct 2023 16:10:14 +0300 (EEST) [thread overview]
Message-ID: <4e5f3519-52a5-179b-1593-80821c2960d0@linux.intel.com> (raw)
In-Reply-To: <51dfe28c-fc47-9f52-6952-3ab2f9a1e668@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2105 bytes --]
On Mon, 9 Oct 2023, Hans de Goede wrote:
> On 10/9/23 14:34, Ilpo Järvinen wrote:
> > On Mon, 9 Oct 2023, Hans de Goede wrote:
> >> On 10/9/23 13:40, Ilpo Järvinen wrote:
> >>> On Fri, 6 Oct 2023, Nikita Kravets wrote:
> >>>
> >>>> This patch adds configurations for new EC firmware from the downstream
> >>>> version of the driver.
> >>>>
> >>>> Cc: Aakash Singh <mail@singhaakash.dev>
> >>>> Cc: Jose Angel Pastrana <japp0005@red.ujaen.es>
> >>>> Signed-off-by: Nikita Kravets <teackot@gmail.com>
> >>>> + .bl_state_address = MSI_EC_ADDR_UNSUPP, // not functional
> >>>
> >>> I only too patch 2/3 becase there seems to be some configuration option
> >>> which causes // comments to trigger warning (that can be made errors
> >>> with another config option) so please use only /* */ comments.
> >>
> >> Hmm, that is very weird all the:
> >>
> >> // SPDX-License-Identifier ...
> >>
> >> comments at the top of many of our .c files are c++ style comments.
> >
> > I know there are those already which is why I didn't think there would
> > have been any problem with them until I got burned.
> >
> > If // comments are okay, what's the explanation for this then:
> >
> > https://lore.kernel.org/oe-kbuild-all/202309270535.g9nOUvFb-lkp@intel.com/
> >
> > It's from randconfig build so it's a bit hard to know from the report
> > itself which CONFIG combination exactly triggers the issue.
> >
> > I can think of two potential ones:
> > a) Only problems for changed lines are reported by LKP
> > b) Header files have different rules than .c files (uapi ones in
> > particular, I'd guess, if that's the case)
>
> Yes I think that the error you point at is caused by the file in question
> being a uapi header. It makes some sense to avoid C++ style comments there
> to e.g. avoid problems when userspace code is build with -ansi .
>
> So I think that uapi headers are the exception to the rule that
> c++ style comments are ok.
Okay, if that's the case, I took this patch into review-ilpo now.
Thank you Nikita for the patch (2 and 3 are now in the review-ilpo
branch).
--
i.
prev parent reply other threads:[~2023-10-09 13:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 17:53 [PATCH v2 0/3] platform/x86: msi-ec: add and fix EC configs Nikita Kravets
2023-10-06 17:53 ` [PATCH v2 1/3] platform/x86: msi-ec: Fix the 3rd config Nikita Kravets
2023-10-09 11:27 ` Ilpo Järvinen
2023-10-11 9:22 ` Hans de Goede
2023-10-06 17:53 ` [PATCH v2 2/3] platform/x86: msi-ec: rename fn_super_swap Nikita Kravets
2023-10-09 11:39 ` Ilpo Järvinen
2023-10-06 17:53 ` [PATCH v2 3/3] platform/x86: msi-ec: Add more EC configs Nikita Kravets
2023-10-09 11:40 ` Ilpo Järvinen
2023-10-09 11:57 ` Hans de Goede
2023-10-09 12:34 ` Ilpo Järvinen
2023-10-09 12:57 ` Hans de Goede
2023-10-09 13:10 ` Ilpo Järvinen [this message]
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=4e5f3519-52a5-179b-1593-80821c2960d0@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=japp0005@red.ujaen.es \
--cc=mail@singhaakash.dev \
--cc=platform-driver-x86@vger.kernel.org \
--cc=teackot@gmail.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