From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Alison Schofield <alison.schofield@intel.com>
Cc: Stefano Brivio <sbrivio@redhat.com>, outreachy@lists.linux.dev
Subject: Re: Compilation errors
Date: Fri, 01 Apr 2022 19:58:28 +0200 [thread overview]
Message-ID: <2937420.687JKscXgg@leap> (raw)
In-Reply-To: <20220401160901.GA1186855@alison-desk>
On venerdì 1 aprile 2022 18:09:01 CEST Alison Schofield wrote:
> On Fri, Apr 01, 2022 at 03:07:24PM +0200, Fabio M. De Francesco wrote:
> > On venerdì 1 aprile 2022 14:57:14 CEST Stefano Brivio wrote:
> > >
> > > Okay, then that's really an error.
> > >
> > > It might simply be that the you're building some drivers on your
> > > staging tree that you're not building on the mainline tree.
> >
> > Yes, this is why I've decided to use the .config that I have in Torvald's
> > tree. They should only differ for the drivers/staging part and the suffix
> > for vmlinuz.
> >
> > Now it builds correctly with gcc11 :)
> >
> > I must look carefully at the diff between the two files and figure out
> > what doesn't work.
> >
> > However what really counts is that now I can go back to work with "staging".
> >
> > Thanks for your time,
> >
> > Fabio
>
> Sounds like you all got things moving along wrt the compile issue.
Yes, thank you. The problem was due to UBSan enabled.
> I do want to follow up on a couple of things buried in this thread.
>
> It's good that compile issue is getting fixed because you can't get
> too far without hitting requirements to build w ALLYESCONFIG or
> ALLMODCONFIG, or the like, while doing kernel development.
>
> The thought of not compiling before sending is blasphemy ;)
I agree in full. It was just the desperation talking :-)
> wrt the 10 patch cleanup requirement. We often have applicants work
> multiple contribution periods for a multitude of reasons. For applicants
> who already have patches accepted in drivers/staging, we ask that they
> submit a few, to show they are current (if needed). Again, if your 'old'
> patches were from last month, no need to prove currency.
Most of my patches (a bit less than 100) are a bit older. The large part of
them are since March 2021 to October 2021. In 2022 I have submitted only
7 patches to net/smc, usb/core, staging.
But I usually don't do clean-ups. For instance, two recent patches were to
fix bugs reported by Syzbot in "net" and in "usb". A couple of recent
"staging" patches are about converting kmap() to kmap_local_page().
> So, Fabio, this means for you personally, go ahead and link to prior
> patches when you record your contribution in the Outreachy application.
Therefore, since the number of recent patches is low, can you please confirm
whether or not I can register also some of those of 2021 "to prove currency"?
Please notice that only 4 or 5 are from the last month.
Thanks,
Fabio
> Anyone else in this situation, please ask.
>
> Thanks,
> Alison
next prev parent reply other threads:[~2022-04-01 17:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 9:35 Compilation errors Fabio M. De Francesco
2022-04-01 10:13 ` Stefano Brivio
2022-04-01 12:01 ` Fabio M. De Francesco
2022-04-01 12:57 ` Stefano Brivio
2022-04-01 13:07 ` Fabio M. De Francesco
2022-04-01 16:09 ` Alison Schofield
2022-04-01 17:58 ` Fabio M. De Francesco [this message]
2022-04-01 14:39 ` Fabio M. De Francesco
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=2937420.687JKscXgg@leap \
--to=fmdefrancesco@gmail.com \
--cc=alison.schofield@intel.com \
--cc=outreachy@lists.linux.dev \
--cc=sbrivio@redhat.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