From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Shyam Saini <shyam.saini@amarulasolutions.com>
Cc: Kernel Hardening <kernel-hardening@lists.openwall.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Kees Cook <keescook@chromium.org>,
linux-arm-kernel@lists.infradead.org,
linux-mips@vger.kernel.org, intel-gvt-dev@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org,
Network Development <netdev@vger.kernel.org>,
linux-ext4@vger.kernel.org, devel@lists.orangefs.org,
linux-mm <linux-mm@kvack.org>,
linux-sctp@vger.kernel.org, bpf <bpf@vger.kernel.org>,
kvm@vger.kernel.org, mayhs11saini@gmail.com
Subject: Re: [PATCH 1/2] include: linux: Regularise the use of FIELD_SIZEOF macro
Date: Sun, 14 Apr 2019 22:43:44 -0700 [thread overview]
Message-ID: <CAADnVQKx5WrUYxr_gSc5ai=fJh2cM9e26NZL1mRPkoSVQxAd0Q@mail.gmail.com> (raw)
In-Reply-To: <20190414091452.22275-1-shyam.saini@amarulasolutions.com>
On Sun, Apr 14, 2019 at 2:15 AM Shyam Saini
<shyam.saini@amarulasolutions.com> wrote:
>
> Currently, there are 3 different macros, namely sizeof_field, SIZEOF_FIELD
> and FIELD_SIZEOF which are used to calculate the size of a member of
> structure, so to bring uniformity in entire kernel source tree lets use
> FIELD_SIZEOF and replace all occurrences of other two macros with this.
>
> For this purpose, redefine FIELD_SIZEOF in include/linux/stddef.h and
> tools/testing/selftests/bpf/bpf_util.h and remove its defination from
> include/linux/kernel.h
>
> Signed-off-by: Shyam Saini <shyam.saini@amarulasolutions.com>
> ---
> arch/arm64/include/asm/processor.h | 10 +++++-----
> arch/mips/cavium-octeon/executive/cvmx-bootmem.c | 2 +-
> drivers/gpu/drm/i915/gvt/scheduler.c | 2 +-
> drivers/net/ethernet/mellanox/mlxsw/spectrum_fid.c | 4 ++--
> fs/befs/linuxvfs.c | 2 +-
> fs/ext2/super.c | 2 +-
> fs/ext4/super.c | 2 +-
> fs/freevxfs/vxfs_super.c | 2 +-
> fs/orangefs/super.c | 2 +-
> fs/ufs/super.c | 2 +-
> include/linux/kernel.h | 9 ---------
> include/linux/slab.h | 2 +-
> include/linux/stddef.h | 11 ++++++++++-
> kernel/fork.c | 2 +-
> kernel/utsname.c | 2 +-
> net/caif/caif_socket.c | 2 +-
> net/core/skbuff.c | 2 +-
> net/ipv4/raw.c | 2 +-
> net/ipv6/raw.c | 2 +-
> net/sctp/socket.c | 4 ++--
> tools/testing/selftests/bpf/bpf_util.h | 11 ++++++++++-
tools/ directory is for user space pieces that don't include kernel's include.
I bet your pathes break the user space builds.
next prev parent reply other threads:[~2019-04-15 5:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 9:14 Shyam Saini
2019-04-14 9:14 ` [PATCH 2/2] include: linux: Remove unused macros and their defination Shyam Saini
2019-04-15 5:43 ` Alexei Starovoitov [this message]
2019-04-15 7:13 ` [PATCH 1/2] include: linux: Regularise the use of FIELD_SIZEOF macro Shyam Saini
2019-04-15 10:12 ` William Kucharski
2019-04-20 10:51 ` Shyam Saini
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='CAADnVQKx5WrUYxr_gSc5ai=fJh2cM9e26NZL1mRPkoSVQxAd0Q@mail.gmail.com' \
--to=alexei.starovoitov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bpf@vger.kernel.org \
--cc=devel@lists.orangefs.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=kvm@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-sctp@vger.kernel.org \
--cc=mayhs11saini@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shyam.saini@amarulasolutions.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