From: Rosen Penev <rosenp@gmail.com>
To: Xu Yilun <yilun.xu@linux.intel.com>
Cc: linux-fpga@vger.kernel.org, Moritz Fischer <mdf@kernel.org>,
Xu Yilun <yilun.xu@intel.com>, Tom Rix <trix@redhat.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] fpga: stratix10-soc: add missing header
Date: Fri, 7 Nov 2025 11:27:02 -0800 [thread overview]
Message-ID: <CAKxU2N-awq-7HRnobmMzssxX6Noo4Y2b3EyFveB0nSOkvXSNMg@mail.gmail.com> (raw)
In-Reply-To: <aQ2Yfh5kWCIJ4VsN@yilunxu-OptiPlex-7050>
On Thu, Nov 6, 2025 at 11:12 PM Xu Yilun <yilun.xu@linux.intel.com> wrote:
>
> On Thu, Nov 06, 2025 at 10:59:37AM -0800, Rosen Penev wrote:
> > linux/sizes.h is needed for SZ_512K.
>
> Does it always fail or only with COMPILE_TEST?
Well, COMPILE_TEST under x86. If I had to guess, this header gets
included from some ARM header.
>
> Please add "fixes" & Cc stable kernel if it always fail.
>
> >
> > Signed-off-by: Rosen Penev <rosenp@gmail.com>
> > ---
> > drivers/fpga/stratix10-soc.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/fpga/stratix10-soc.c b/drivers/fpga/stratix10-soc.c
> > index 0a295ccf1644..ab309cbf21c6 100644
> > --- a/drivers/fpga/stratix10-soc.c
> > +++ b/drivers/fpga/stratix10-soc.c
> > @@ -11,6 +11,7 @@
> > #include <linux/of.h>
> > #include <linux/of_platform.h>
> > #include <linux/platform_device.h>
> > +#include <linux/sizes.h>
> >
> > /*
> > * FPGA programming requires a higher level of privilege (EL3), per the SoC
> > --
> > 2.51.2
> >
> >
next prev parent reply other threads:[~2025-11-07 19:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 18:59 [PATCH 0/2] fpga: stratix10-soc: fix compilation + COMPILE_TEST Rosen Penev
2025-11-06 18:59 ` [PATCH 1/2] fpga: stratix10-soc: add missing header Rosen Penev
2025-11-07 6:58 ` Xu Yilun
2025-11-07 19:27 ` Rosen Penev [this message]
2025-11-06 18:59 ` [PATCH 2/2] fpga: stratix10-soc: add COMPILE_TEST support Rosen Penev
2025-11-07 7:16 ` Xu Yilun
2025-11-07 19:28 ` Rosen Penev
2025-11-08 4:01 ` Xu Yilun
2025-11-10 20:24 ` Rosen Penev
2025-11-10 3:21 ` kernel test robot
2025-11-10 16:44 ` kernel test robot
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=CAKxU2N-awq-7HRnobmMzssxX6Noo4Y2b3EyFveB0nSOkvXSNMg@mail.gmail.com \
--to=rosenp@gmail.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.com \
--cc=yilun.xu@linux.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).