From: Josef Bacik <josef@toxicpanda.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, brauner@kernel.org,
linux-fsdevel@vger.kernel.org, mszeredi@redhat.com,
kernel-team@fb.com
Subject: Re: [PATCH v2 0/2] man-pages: add documentation for statmount/listmount
Date: Wed, 26 Jun 2024 17:50:34 -0400 [thread overview]
Message-ID: <20240626215034.GA3606318@perftesting> (raw)
In-Reply-To: <20240626214407.GA3602100@perftesting>
On Wed, Jun 26, 2024 at 05:44:07PM -0400, Josef Bacik wrote:
> On Wed, Jun 26, 2024 at 08:41:06PM +0200, Alejandro Colomar wrote:
> > Hi Josef,
> >
> > On Wed, Jun 26, 2024 at 02:04:34PM GMT, Josef Bacik wrote:
> > > On Wed, Jun 26, 2024 at 07:02:26PM +0200, Alejandro Colomar wrote:
> > > > You can
> > > >
> > > > $ make lint build check -j8 -k
> > > > $ make lint build check
> > > >
> > > > to see the full list of failures.
> > >
> > > I captured the output of
> > >
> > > make lint build check -j8 -k > out.txt 2>&1
> >
> > Hmmm, please do the following steps to have a cleaner log:
> >
> > ## Let's see if the build system itself complains:
> > $ make nothing >out0.txt
> >
> > ## Skip checkpatch stuff:
> > $ make -t lint-c-checkpatch
> >
> > ## Make fast stuff that doesn't break:
> > $ make lint build check -j8 -k >/dev/null 2>/dev/null
> >
> > ## Now log the remaining errors:
> > $ make lint build check >out.txt 2>&1
> >
> > > and pasted it here
> > >
> > > https://paste.centos.org/view/ed3387a9
> >
> > BTW, you seem to also be missing cppcheck(1), which at least in Debian
> > is provided in the cppcheck package. It also seems to be available in
> > Fedora, but I don't know if your system will have it.
> >
> > > Clang messes up a bunch for a variety of different pages.
> >
> > I suspect the Clang errors to be due to missing libbsd-dev.
> >
>
> Ok well those two things fixed most of the errors, now I'm down to just this
>
> https://paste.centos.org/view/acd71eb7
>
Err that just shows the one error, this is all of them
https://paste.centos.org/view/b68c2fb1
Thanks,
Josef
next prev parent reply other threads:[~2024-06-26 21:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 15:56 [PATCH v2 0/2] man-pages: add documentation for statmount/listmount Josef Bacik
2024-06-26 15:56 ` [PATCH v2 1/2] statmount.2: New page describing the statmount syscall Josef Bacik
2024-06-26 15:56 ` [PATCH v2 2/2] listmount.2: New page describing the listmount syscall Josef Bacik
2024-06-26 17:02 ` [PATCH v2 0/2] man-pages: add documentation for statmount/listmount Alejandro Colomar
2024-06-26 18:04 ` Josef Bacik
2024-06-26 18:41 ` Alejandro Colomar
2024-06-26 21:44 ` Josef Bacik
2024-06-26 21:50 ` Josef Bacik [this message]
2024-06-26 22:02 ` Alejandro Colomar
2024-06-26 22:06 ` Alejandro Colomar
2024-06-26 21:58 ` Alejandro Colomar
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=20240626215034.GA3606318@perftesting \
--to=josef@toxicpanda.com \
--cc=alx@kernel.org \
--cc=brauner@kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mszeredi@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 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.