From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <thomas@t-8ch.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools/nolibc: remove LINUX_REBOOT_ constants
Date: Tue, 2 May 2023 09:20:36 +0200 [thread overview]
Message-ID: <ZFC5xHVNEfyXtbLS@1wt.eu> (raw)
In-Reply-To: <781b8ce2-bc3e-4eef-b466-fc0e26f64bb5@t-8ch.de>
On Tue, May 02, 2023 at 09:05:29AM +0200, Thomas Weißschuh wrote:
> On 2023-05-02 08:59:27+0200, Willy Tarreau wrote:
>
> <snip>
>
> > > The following trivial fix on top of my patch would fix the problem:
> > >
> > > diff --git a/tools/include/nolibc/sys.h b/tools/include/nolibc/sys.h
> > > index 5d624dc63a42..9d27131c224e 100644
> > > --- a/tools/include/nolibc/sys.h
> > > +++ b/tools/include/nolibc/sys.h
> > > @@ -21,6 +21,7 @@
> > > #include <linux/auxvec.h>
> > > #include <linux/fcntl.h> // for O_* and AT_*
> > > #include <linux/stat.h> // for statx()
> > > +#include <linux/reboot.h> // for LINUX_REBOOT_*
> > >
> > > #include "arch.h"
> > > #include "errno.h"
> >
> > Indeed it works for me as well.
> >
> > > Want me to send a v2 or will you fix it up on your side?
> >
> > It depends. If for you it's a fix and needed for 6.4 (or maybe older),
> > then that one is needed with the "//" comment, and it will later
> > conflict with your previous cleanup patch that's already queued. If
> > you're fine with having it queued for 6.5 only however, then I'll just
> > edit your patch and add that above. I tend to think the second solution
> > is sufficient given that nobody complained till now ;-)
>
> This is absolutely not urgent. 6.5 is fine.
OK, now queued on top of my 20230415-nolibc-updates-4a branch that
I'll soon send to Paul.
Thank you!
Willy
prev parent reply other threads:[~2023-05-02 7:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 15:52 [PATCH] tools/nolibc: remove LINUX_REBOOT_ constants Thomas Weißschuh
2023-05-02 6:32 ` Willy Tarreau
2023-05-02 6:47 ` Thomas Weißschuh
2023-05-02 6:59 ` Willy Tarreau
2023-05-02 7:05 ` Thomas Weißschuh
2023-05-02 7:20 ` Willy Tarreau [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=ZFC5xHVNEfyXtbLS@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@t-8ch.de \
/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.