From: Christian Marangi <ansuelsmth@gmail.com>
To: Quentin Schulz <quentin.schulz@cherry.de>
Cc: Dario Binacchi <dario.binacchi@amarulasolutions.com>,
Michael Trimarchi <michael@amarulasolutions.com>,
Frieder Schrempf <frieder.schrempf@kontron.de>,
Tom Rini <trini@konsulko.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH 1/2] linux/bitfield.h: import FIELD_PREP_CONST macro from Linux Kernel
Date: Tue, 3 Jun 2025 22:37:22 +0200 [thread overview]
Message-ID: <683f5d03.df0a0220.437bb.ca9c@mx.google.com> (raw)
In-Reply-To: <d272087c-4f0d-406f-9630-57fc1c68b403@cherry.de>
On Tue, Jun 03, 2025 at 05:08:13PM +0200, Quentin Schulz wrote:
> Hi Christian,
>
> On 6/3/25 10:51 AM, Christian Marangi wrote:
> > Import FIELD_PREP_CONST macro from Linux Kernel to permit usage of
> > FIELD_PREP with scenario where a constant value is needed.
> >
> > Refer to commit e2192de59e45 ("bitfield: add FIELD_PREP_CONST()") in
> > Linux kernel for extensive explaination of why this is useful.
> >
> > This is also to better align with the Linux Kernel for easier porting of
> > driver.
> >
>
> Do you know it it'd be possible to simply copy Linux kernel's bitfield.h
> instead of "cherry-picking" individual commit(s)?
>
Mhhh what do you mean? You mean syncing the full header with latest
version?
Isn't that more risky??
--
Ansuel
next prev parent reply other threads:[~2025-06-03 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 8:51 [PATCH 1/2] linux/bitfield.h: import FIELD_PREP_CONST macro from Linux Kernel Christian Marangi
2025-06-03 8:51 ` [PATCH 2/2] mtd: spinand: winbond: add Winbond W25N04KV flash support Christian Marangi
2025-06-03 15:08 ` [PATCH 1/2] linux/bitfield.h: import FIELD_PREP_CONST macro from Linux Kernel Quentin Schulz
2025-06-03 20:37 ` Christian Marangi [this message]
2025-06-03 23:50 ` Tom Rini
2025-06-04 8:55 ` Quentin Schulz
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=683f5d03.df0a0220.437bb.ca9c@mx.google.com \
--to=ansuelsmth@gmail.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=frieder.schrempf@kontron.de \
--cc=michael@amarulasolutions.com \
--cc=quentin.schulz@cherry.de \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.