From: Len Baker <len.baker@gmx.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Len Baker <len.baker@gmx.com>, Daniel Vetter <daniel@ffwll.ch>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
David Airlie <airlied@linux.ie>,
Kees Cook <keescook@chromium.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/i915: Prefer struct_size over open coded arithmetic
Date: Sat, 30 Oct 2021 09:51:50 +0200 [thread overview]
Message-ID: <20211030075150.GA3486@titan> (raw)
In-Reply-To: <87ee86h5hn.fsf@intel.com>
Hi,
On Wed, Oct 27, 2021 at 06:06:28PM +0300, Jani Nikula wrote:
> On Sat, 23 Oct 2021, Len Baker <len.baker@gmx.com> wrote:
> > Sorry, but I'm missing something here. In linux-next this is the commit
> > history of include/linux/stddef.h file:
> >
> > 3080ea5553cc stddef: Introduce DECLARE_FLEX_ARRAY() helper
> > 50d7bd38c3aa stddef: Introduce struct_group() helper macro
> > e7f18c22e6be stddef: Fix kerndoc for sizeof_field() and offsetofend()
> > 4229a470175b stddef.h: Introduce sizeof_field()
> > ...
> >
> > But in drm-tip this is the commit history:
> >
> > 4229a470175b stddef.h: Introduce sizeof_field()
> > ...
> >
> > For this patch the DECLARE_FLEX_ARRAY() helper is needed. But the build
> > fails due to the last tree commits for stddef.h file are not present.
> > So, if I understand correctly, drm-tip is not up to date with linux-next.
>
> linux-next is an ephemeral integration branch for most arch, subsystem
> and driver -next branches.
>
> drm-tip is an ephemeral integration branch for drm subsystem and driver
> -next branches.
>
> They contain different sets of branches. They are constantly
> rebuilt. They are not the end result or end goal.
>
> If a problem (or a solution, for that matter) only exists in the merge
> of some of those branches, you can't actually fix it until such a merge
> exists somewhere more permanent than an ephemeral integration branch.
Ok, understood. Thanks for the clarification.
Regards,
Len
prev parent reply other threads:[~2021-10-30 7:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 10:42 [PATCH] drm/i915: Prefer struct_size over open coded arithmetic Len Baker
2021-10-11 9:23 ` Len Baker
2021-10-13 11:24 ` Jani Nikula
2021-10-13 11:51 ` Daniel Vetter
2021-10-16 11:16 ` Len Baker
2021-10-18 10:00 ` Jani Nikula
2021-10-23 11:50 ` Len Baker
2021-10-27 15:06 ` Jani Nikula
2021-10-30 7:51 ` Len Baker [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=20211030075150.GA3486@titan \
--to=len.baker@gmx.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavoars@kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.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;
as well as URLs for NNTP newsgroup(s).