From: Joe Damato <jdamato@fastly.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 1/1] ioctl_epoll.2: New page describing ioctl(2) operations for epoll fds
Date: Mon, 10 Jun 2024 10:29:44 -0700 [thread overview]
Message-ID: <Zmc4CCQxwY3D6z1e@LQ3V64L9R2> (raw)
In-Reply-To: <jslixhueinkq3uuoeudezrri6qp4vxoa4sp25juklgryk47ktw@tbiz6lk7mmh4>
On Sun, Jun 09, 2024 at 07:04:40PM +0200, Alejandro Colomar wrote:
> Hi Joe,
>
> On Fri, Jun 07, 2024 at 02:53:19PM GMT, Joe Damato wrote:
> > On Thu, Jun 06, 2024 at 11:46:47PM +0200, Alejandro Colomar wrote:
> > > $ make lint build check -j24
> > > GROTTY .tmp/man/man2/epoll_create.2.cat
> > > GROTTY .tmp/man/man2/epoll_ctl.2.cat
> > > TROFF .tmp/man/man2/ioctl_epoll.2.cat.set
> > > an.tmac:.tmp/man/man2/ioctl_epoll.2:61: style: blank line in input
> > > make: *** [/home/alx/src/linux/man-pages/man-pages/contrib/share/mk/build/catman/troff.mk:63: .tmp/man/man2/ioctl_epoll.2.cat.set] Error 1
> > > make: *** Deleting file '.tmp/man/man2/ioctl_epoll.2.cat.set'
> >
> > Hmm..
> >
> > When I run make I get an error:
> >
> > $ make
> > TROFF .tmp/man/man2/s390_sthyi.2.cat.set
> > troff: .tmp/man/man2/s390_sthyi.2:124: warning [p 2, 2.8i]: cannot adjust line
>
> Hmm, I can't reproduce it. Can you run with `make --debug=print` (needs
> a recent make(1))?
I don't think I have a recent enough make:
$ make --debug=print
make: *** unknown debug level specification 'print'. Stop.
$ make --version
GNU Make 4.3
> > I tried to run the lint build check target and got an error about
> > checkpatch:
> >
> > $ make lint build check -j8
> > CHECKPATCH .tmp/man/man2/fork.2.d/fork.c.lint-c.checkpatch.touch
> > bash: line 1: checkpatch: command not found
> >
> > I have mandoc, groff, and clang-tidy installed, but maybe I'm
> > missing other dependency?
>
> That's a fork of the checkpatch.pl from the kernel. I'm working on a
> repository to make it public. Don't worry about it.
>
> You can `make -t lint-c-checkpatch` to ignore all checkpatch lints.
$ make -t lint-c-checkpatch
$ echo $?
0
Does that mean I'm good to go and ready to submit v2 ? ;)
>
> Have a lovely day!
> Alex
>
> --
> <https://www.alejandro-colomar.es/>
next prev parent reply other threads:[~2024-06-10 17:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 18:17 [PATCH 0/1] ioctl_epoll.2: Add epoll ioctl documentation Joe Damato
2024-06-04 18:17 ` [PATCH 1/1] ioctl_epoll.2: New page describing ioctl(2) operations for epoll fds Joe Damato
2024-06-06 21:39 ` Alejandro Colomar
2024-06-06 21:46 ` Alejandro Colomar
2024-06-07 21:53 ` Joe Damato
2024-06-09 17:04 ` Alejandro Colomar
2024-06-10 17:29 ` Joe Damato [this message]
2024-06-10 18:24 ` Alejandro Colomar
2024-06-10 20:16 ` Joe Damato
2024-06-10 22:21 ` Alejandro Colomar
2024-06-11 12:39 ` G. Branden Robinson
2024-06-11 14:34 ` Alejandro Colomar
2024-06-11 16:06 ` G. Branden Robinson
2024-06-11 16:42 ` Alejandro Colomar
2024-06-07 2:06 ` Joe Damato
2024-06-07 10:29 ` Alejandro Colomar
2024-06-07 21:56 ` Joe Damato
2024-06-06 21:44 ` [PATCH 0/1] ioctl_epoll.2: Add epoll ioctl documentation Alejandro Colomar
2024-06-06 22:14 ` Joe Damato
2024-06-06 22:25 ` Alejandro Colomar
2024-06-07 2:08 ` Joe Damato
2024-06-07 10:44 ` 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=Zmc4CCQxwY3D6z1e@LQ3V64L9R2 \
--to=jdamato@fastly.com \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
/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