All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <iwj@xenproject.org>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: <xen-devel@lists.xenproject.org>, Wei Liu <wl@xen.org>,
	Juergen Gross <jgross@suse.com>
Subject: Re: [PATCH for-4.15] autoconf: check endian.h include path
Date: Thu, 4 Feb 2021 11:34:57 +0000	[thread overview]
Message-ID: <24603.56289.723251.263900@mariner.uk.xensource.com> (raw)
In-Reply-To: <20210204093833.91190-1-roger.pau@citrix.com>

Roger Pau Monne writes ("[PATCH for-4.15] autoconf: check endian.h include path"):
> Introduce an autoconf macro to check for the include path of certain
> headers that can be different between OSes.
> 
> Use such macro to find the correct path for the endian.h header, and
> modify the users of endian.h to use the output of such check.
> 
> Suggested-by: Ian Jackson <iwj@xenproject.org>
> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>

Reviewed-by: Ian Jackson <iwj@xenproject.org>

> Please re-run autogen after applying.
> 
> The biggest risk for this would be some kind of configure or build
> failure, and we should be able to catch it in either osstest or the
> gitlab build tests.

Thanks.  I agree.

Release-Acked-by: Ian Jackson <iwj@xenproject.org>


      parent reply	other threads:[~2021-02-04 11:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-04  9:38 [PATCH for-4.15] autoconf: check endian.h include path Roger Pau Monne
2021-02-04  9:46 ` Jan Beulich
2021-02-04  9:59   ` Roger Pau Monné
2021-02-04 10:13     ` Jan Beulich
2021-02-04 10:21       ` Roger Pau Monné
2021-02-04 10:32         ` Jan Beulich
2021-02-04 10:48           ` Roger Pau Monné
2021-02-04 11:37             ` Ian Jackson
2021-02-04 11:34 ` Ian Jackson [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=24603.56289.723251.263900@mariner.uk.xensource.com \
    --to=iwj@xenproject.org \
    --cc=jgross@suse.com \
    --cc=roger.pau@citrix.com \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.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 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.