From: David Sterba <dsterba@suse.cz>
To: filipbystricky@google.com
Cc: linux-btrfs@vger.kernel.org, salyzyn@android.com
Subject: Re: [PATCH 1/3] copied android.mk from devel branch
Date: Tue, 15 Aug 2017 15:21:03 +0200 [thread overview]
Message-ID: <20170815132103.GA2866@twin.jikos.cz> (raw)
In-Reply-To: <20170802185111.187922-1-filipbystricky@google.com>
On Wed, Aug 02, 2017 at 11:51:09AM -0700, filipbystricky@google.com wrote:
> From: Filip Bystricky <filipbystricky@google.com>
>
> This series of patches fixes some compile errors that trigger when
> compiling to android devices.
>
> This first patch just brings in devel's Android.mk, to which
> kdave@ added a few fixes recently.
>
> Signed-off-by: Filip Bystricky <filipbystricky@google.com>
> Reviewed-by: Mark Salyzyn <salyzyn@android.com>
The changes in this patch are already applied in current master or devel
branch, so the resulting diff is empty. The patches 2 and 3 bring the
real fixes so I'm going to apply them but patch 2 lacks the changelog.
It should briefly describe the type of changes.
As you've probably fixed the current compilation issues, I'd like to
avoid future breakage when we update the standard Makefile. The travis
CI could be used in connection with the docker images, but I'm open to
other suggestions to do verify builds in other CI systems if there's
some already established practice.
prev parent reply other threads:[~2017-08-15 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 18:51 [PATCH 1/3] copied android.mk from devel branch filipbystricky
2017-08-02 18:51 ` [PATCH 2/3] fixed android.mk filipbystricky
2017-08-02 18:51 ` [PATCH 3/3] compile error fixes filipbystricky
2017-08-15 13:21 ` David Sterba [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=20170815132103.GA2866@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=filipbystricky@google.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=salyzyn@android.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).