public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ole Schuerks <ole0811sch@gmail.com>
To: masahiroy@kernel.org
Cc: deltaone@debian.org, jan.sollmann@rub.de, jude.gyimah@rub.de,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	mcgrof@kernel.org, ole0811sch@gmail.com, thorsten.berger@rub.de
Subject: Re: [PATCH v4 07/12] kconfig: Add files for handling expressions
Date: Fri, 16 Aug 2024 12:23:19 +0200	[thread overview]
Message-ID: <20240816102319.21739-1-ole0811sch@gmail.com> (raw)
In-Reply-To: <CAK7LNARA2W41X2n97O-=TXYPrmTsGqL-aMczPHsB2T_Y3QOGrA@mail.gmail.com>

On 8/12/24 10:46, Masahiro Yamada wrote:
> On Wed, Jul 10, 2024 at 3:54 PM Ole Schuerks <ole0811sch@gmail.com> wrote:
>>
>> To translate the Kconfig-model into propositional logic and resolve
>> conflicts, we need to handle propostional formulas.
>> These files contain many functions and macros to deal with
>> propositional formulas.
>>
>> Co-developed-by: Patrick Franz <deltaone@debian.org>
>> Signed-off-by: Patrick Franz <deltaone@debian.org>
>> Co-developed-by: Ibrahim Fayaz <phayax@gmail.com>
>> Signed-off-by: Ibrahim Fayaz <phayax@gmail.com>
>> Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>
>> Tested-by: Evgeny Groshev <eugene.groshev@gmail.com>
>> Suggested-by: Sarah Nadi <nadi@ualberta.ca>
>> Suggested-by: Thorsten Berger <thorsten.berger@rub.de>
>> Signed-off-by: Thorsten Berger <thorsten.berger@rub.de>
>> Signed-off-by: Ole Schuerks <ole0811sch@gmail.com>
>> ---
>>  scripts/kconfig/cf_expr.c | 2594 +++++++++++++++++++++++++++++++++++++
>>  scripts/kconfig/cf_expr.h |  296 +++++
>>  2 files changed, 2890 insertions(+)
>>  create mode 100644 scripts/kconfig/cf_expr.c
>>  create mode 100644 scripts/kconfig/cf_expr.h

>> +/*
>> + * convert a fexpr to a pexpr
>> + */
>> +struct pexpr *pexf(struct fexpr *fe)
>
>
>
>
> Not only this one, but more descriptive function name please.
>
> "pexf", so what?
> I do not understand what it is doing from the name.
>
>

Could you give us one or two examples of what other functions have bad 
names? I didn't find anything as bad as pexf() so I'm not sure what the 
expectations are. Thank you, that would be helpful.

  reply	other threads:[~2024-08-16 10:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-10  6:52 [PATCH v4 00/12] kconfig: Add support for conflict resolution Ole Schuerks
2024-07-10  6:52 ` [PATCH v4 01/12] kconfig: Add picosat.h Ole Schuerks
2024-07-10  6:52 ` [PATCH v4 02/12] kconfig: Add picosat.c (1/3) Ole Schuerks
2024-08-12  8:41   ` Masahiro Yamada
2024-08-16 10:20     ` Ole Schuerks
2024-08-19 22:04       ` Luis Chamberlain
2024-08-29 21:23         ` Ole Schuerks
2024-09-05  8:55           ` Luis Chamberlain
2024-09-20  9:07             ` Ole Schuerks
2024-07-10  6:52 ` [PATCH v4 03/12] kconfig: Add picosat.c (2/3) Ole Schuerks
2024-07-10  6:52 ` [PATCH v4 04/12] kconfig: Add picosat.c (3/3) Ole Schuerks
2024-07-10  6:52 ` [PATCH v4 05/12] kconfig: Add definitions Ole Schuerks
2024-07-10  6:52 ` [PATCH v4 06/12] kconfig: Add files for building constraints Ole Schuerks
2024-08-12  8:49   ` Masahiro Yamada
2024-08-12 10:00     ` Masahiro Yamada
2024-07-10  6:52 ` [PATCH v4 07/12] kconfig: Add files for handling expressions Ole Schuerks
2024-08-12  8:46   ` Masahiro Yamada
2024-08-16 10:23     ` Ole Schuerks [this message]
2024-07-10  6:52 ` [PATCH v4 08/12] kconfig: Add files for RangeFix Ole Schuerks
2024-07-10  6:52 ` [PATCH v4 09/12] kconfig: Add files with utility functions Ole Schuerks
2024-08-12  8:48   ` Masahiro Yamada
2024-07-10  6:52 ` [PATCH v4 10/12] kconfig: Add tools Ole Schuerks
2024-07-10  6:52 ` [PATCH v4 11/12] kconfig: Add xconfig-modifications Ole Schuerks
2024-08-12  9:28   ` Masahiro Yamada
2024-07-10  6:52 ` [PATCH v4 12/12] kconfig: Add loader.gif Ole Schuerks

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=20240816102319.21739-1-ole0811sch@gmail.com \
    --to=ole0811sch@gmail.com \
    --cc=deltaone@debian.org \
    --cc=jan.sollmann@rub.de \
    --cc=jude.gyimah@rub.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=thorsten.berger@rub.de \
    /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