From: Thomas Huth <thuth@redhat.com>
To: Will Cohen <wwcohen@gmail.com>, Peter Maydell <peter.maydell@linaro.org>
Cc: "Fabian Franz" <fabianfranz.oss@gmail.com>,
"Christian Schoenebeck" <qemu_oss@crudebyte.com>,
"qemu Developers" <qemu-devel@nongnu.org>,
"Greg Kurz" <groug@kaod.org>,
"Keno Fischer" <keno@juliacomputing.com>,
"Michael Roitzsch" <reactorcontrol@icloud.com>,
"Philippe Mathieu-Daudé" <philippe.mathieu.daude@gmail.com>,
hi@alyssa.is
Subject: Re: [PATCH v2] 9p: move P9_XATTR_SIZE_MAX from 9p.h to 9p.c
Date: Fri, 1 Apr 2022 13:01:31 +0200 [thread overview]
Message-ID: <fa63b692-a1be-d4f9-d2ee-e8e4c1af4890@redhat.com> (raw)
In-Reply-To: <CAB26zV2UkS4unxXkTLiF8T5aY9YaCpcUd2DRbzb0_FHTt+uyyw@mail.gmail.com>
On 31/03/2022 22.06, Will Cohen wrote:
> On Thu, Mar 31, 2022 at 4:00 PM Peter Maydell <peter.maydell@linaro.org
> <mailto:peter.maydell@linaro.org>> wrote:
>
> On Thu, 31 Mar 2022 at 19:27, Will Cohen <wwcohen@gmail.com
> <mailto:wwcohen@gmail.com>> wrote:
> >
> > The patch set adding 9p functionality to darwin introduced an issue
> > where limits.h, which defines XATTR_SIZE_MAX, is included in 9p.c,
> > though the referenced constant is needed in 9p.h. This commit fixes that
> > issue by moving the definition of P9_XATTR_SIZE_MAX, which uses
> > XATTR_SIZE_MAX, to also be in 9p.c.
> >
> > Additionally, this commit moves the location of the system headers
> > include in 9p.c to occur before the project headers.
> >
> > Resolves: https://gitlab.com/qemu-project/qemu/-/issues/950
> <https://gitlab.com/qemu-project/qemu/-/issues/950>
> > Fixes: 38d7fd68b0 ("9p: darwin: Move XATTR_SIZE_MAX->P9_XATTR_SIZE_MAX")
> >
> > Signed-off-by: Will Cohen <wwcohen@gmail.com <mailto:wwcohen@gmail.com>>
> > ---
> > hw/9pfs/9p.c | 28 +++++++++++++++++++++++-----
> > hw/9pfs/9p.h | 18 ------------------
> > 2 files changed, 23 insertions(+), 23 deletions(-)
> >
> > diff --git a/hw/9pfs/9p.c b/hw/9pfs/9p.c
> > index dcaa602d4c..b9152c7882 100644
> > --- a/hw/9pfs/9p.c
> > +++ b/hw/9pfs/9p.c
> > @@ -16,6 +16,11 @@
> > * https://wiki.qemu.org/Documentation/9p
> <https://wiki.qemu.org/Documentation/9p>
> > */
> >
> > +#ifdef CONFIG_LINUX
> > +#include <linux/limits.h>
> > +#else
> > +#include <limits.h>
> > +#endif
> > #include "qemu/osdep.h"
>
> osdep.h must always be the first include line in any .c file.
>
> Understood, apologies -- if there's other changes for a v3 I can resubmit
> accordingly, but if this otherwise looks okay then I would be fine with a
> QEMU maintainer adjusting the header placement as needed when preparing for
> submission to the main tree.
Makes sense. I'm currently assembling a pull req with some misc fixes for
7.0 ... if Christian & Greg do not have any other patches pending right now,
I could throw this in, with the osdep.h location fixed.
Thomas
next prev parent reply other threads:[~2022-04-01 11:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 18:26 [PATCH v2] 9p: move P9_XATTR_SIZE_MAX from 9p.h to 9p.c Will Cohen
2022-03-31 20:00 ` Peter Maydell
2022-03-31 20:06 ` Will Cohen
2022-04-01 11:01 ` Thomas Huth [this message]
2022-04-01 11:24 ` Christian Schoenebeck
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=fa63b692-a1be-d4f9-d2ee-e8e4c1af4890@redhat.com \
--to=thuth@redhat.com \
--cc=fabianfranz.oss@gmail.com \
--cc=groug@kaod.org \
--cc=hi@alyssa.is \
--cc=keno@juliacomputing.com \
--cc=peter.maydell@linaro.org \
--cc=philippe.mathieu.daude@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.com \
--cc=reactorcontrol@icloud.com \
--cc=wwcohen@gmail.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;
as well as URLs for NNTP newsgroup(s).