From: Joel Brobecker <brobecker@adacore.com>
To: Lukas Durfina <ldurfina@tachyum.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdb/testsuite: Updated includes
Date: Tue, 07 Jan 2020 17:55:00 -0000 [thread overview]
Message-ID: <20200107175458.GA31232@adacore.com> (raw)
In-Reply-To: <c883d51c0b3f44e49fa9f6a9088b1355@tachyum.com>
> > I see you removed the <sys/errno.h> #include without replacing it by a
> > #include of <errno.h>. However, this file does make references to errno, so I
> > think there is an oversight there.
>
> There is already #include <errno.h> a few lines below, so I skipped it.
Duh (head slap). <accent=french>but of course</accent>. Sorry.
> > Also, I see you not only replace <sys/fcntl.h> by <fcntl.h>, but you also move
> > its include further down. Any reason for that.
> > Was it to move that include outside of the range of #include-s that include
> > files in "sys"?
>
> Exactly. My intention was to move it out of <sys/...> includes. No
> other reason.
>
> >
> > For the ChangeLog, I think it is worth being a little more specific.
> > For instance, I would have written the ChangeLog as follow:
> >
> > * gdb.base/fileio.c: Remove #include of <sys/errno.h>.
> > Replace #include of <sys/fcntl.h> by <fcntl.h>.
> >
> > I'm usually the first in line to take shortcuts with ChangeLog
> > files, but I try to be more informative when the cost of being so is
> > so small...
>
> I see your point. Is it fine to send the patch with updated Changelog?
That would be fine. On the other hand, if you want, you can push
the patch with the ChangeLog above, since the change itself looks
good to me, now.
Thank you!
>
> Lukas
>
> >
> > > +
> > > 2019-12-29 Bernd Edlinger <bernd.edlinger@hotmail.de>
> > >
> > > * gdb.base/line65535.exp: New file.
> > > diff --git a/gdb/testsuite/gdb.base/fileio.c
> > > b/gdb/testsuite/gdb.base/fileio.c index 7f482a34d3..0f201518b7 100644
> > > --- a/gdb/testsuite/gdb.base/fileio.c
> > > +++ b/gdb/testsuite/gdb.base/fileio.c
> > > @@ -1,13 +1,12 @@
> > > #include <stdio.h>
> > > #include <stdlib.h>
> > > #include <string.h>
> > > -#include <sys/errno.h>
> > > #include <sys/types.h>
> > > -#include <sys/fcntl.h>
> > > #include <sys/stat.h>
> > > #include <sys/time.h>
> > > #include <errno.h>
> > > #include <sys/wait.h>
> > > +#include <fcntl.h>
> > > #include <unistd.h>
> > > #include <time.h>
> > > /* TESTS :
> > > --
> > > 2.17.1
> >
> > --
> > Joel
--
Joel
next prev parent reply other threads:[~2020-01-07 17:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 14:47 Lukas Durfina
2020-01-05 6:25 ` Joel Brobecker
2020-01-07 13:48 ` Lukas Durfina
2020-01-07 17:55 ` Joel Brobecker [this message]
2020-01-09 8:17 ` Lukas Durfina
2020-02-01 10:15 ` Joel Brobecker
2020-02-03 10:00 ` Lukas Durfina
2020-02-03 10:25 ` Joel Brobecker
2020-02-03 10:10 ` [PATCH] [gdb/testsuite] Fix compilation error with musl in gdb/testsuite/gdb.base/fileio.c Lukas Durfina
2020-02-03 10:37 ` Joel Brobecker
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=20200107175458.GA31232@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=ldurfina@tachyum.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