All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: linux-ext4@vger.kernel.org
Subject: [PATCH 0/3] e2fsprogs: test cross-compiling for Android
Date: Tue, 21 Mar 2023 20:29:42 -0700	[thread overview]
Message-ID: <20230322032945.31779-1-ebiggers@kernel.org> (raw)

This series adds jobs to .github/workflows/ci.yml that cross-compile
e2fsprogs for Android.  To make that possible, it also fixes a couple
warnings and an error that show up when building e2fsprogs for Android
using the autotools-based build system.

This applies to the latest 'maint' branch.  I've tested that the updated
GitHub Actions workflow passes
(https://github.com/ebiggers/e2fsprogs/actions/runs/4486115058).

Eric Biggers (3):
  e2fsck: avoid -Wtautological-constant-out-of-range-compare warnings
  e2freefrag: don't use linux/fsmap.h when fsmap_sizeof() is missing
  ci.yml: test cross-compiling for Android

 .github/workflows/ci.yml | 33 +++++++++++++++
 configure                | 91 ++++++++++++++++++++++++++--------------
 configure.ac             |  6 +++
 e2fsck/iscan.c           |  3 +-
 e2fsck/util.c            |  3 +-
 lib/config.h.in          |  3 ++
 misc/e2freefrag.c        |  2 +-
 7 files changed, 107 insertions(+), 34 deletions(-)


base-commit: cbc6a5ae4f350bfb0dd0daa39544615a5d0a956a
-- 
2.40.0


             reply	other threads:[~2023-03-22  3:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22  3:29 Eric Biggers [this message]
2023-03-22  3:29 ` [PATCH 1/3] e2fsck: avoid -Wtautological-constant-out-of-range-compare warnings Eric Biggers
2023-03-22  3:29 ` [PATCH 2/3] e2freefrag: don't use linux/fsmap.h when fsmap_sizeof() is missing Eric Biggers
2023-03-22  3:29 ` [PATCH 3/3] ci.yml: test cross-compiling for Android Eric Biggers

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=20230322032945.31779-1-ebiggers@kernel.org \
    --to=ebiggers@kernel.org \
    --cc=linux-ext4@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 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.