From: Benda Xu <heroxbd@gentoo.org>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] Weekly report 04/30
Date: Wed, 02 May 2018 17:21:07 +0800 [thread overview]
Message-ID: <87bmdyl8fw.fsf@gentoo.org> (raw)
In-Reply-To: <1e2101d3e0a0$b0383860$10a8a920$@jsteward.moe> (Pengcheng Xu's message of "Tue, 1 May 2018 00:31:17 +0800")
[-- Attachment #1: Type: text/plain, Size: 1627 bytes --]
Hi Pengcheng,
Looks good to me. Looking forward to your UART and init hacks.
"Pengcheng Xu" <i@jsteward.moe> writes:
> My daily activities this week sums up as follows:
>
> April 25: updated local Lineage OS source tree, tried to figure out
> reason of compile failure
> April 26: scrolled back in AOSP compile log to find error, fixed error
> by cleaning work directory
> April 27: successfully compiled ROM package, backed-up old data on
> phone
> April 28: installed fastboot driver on Windows, flashed newest TWRP,
> flashed ROM package, tested for functionality
> April 29: tweaked kernel options (fixing compile errors in the
> process), added hook before initramfs generation, set up GitHub repo
> forks
> April 30: blogged about progress, cleaned up bookmarks for articles to
> read
Will you please add the reference articles in your blog post?
> The blog post that logs the details is at [1].
>
> Thanks in advance!
>
> [1]: https://jsteward.moe/weekly-report-0430.html
> Some compile errors (such as missing semi-colons and #include's) pop
> up as I enable options in kernel config. (This clearly demonstrates
> Google's poor code quality :/ ) I've forked the kernel repository on
> GitHub to store my changes to the kernel source.
Is it possible to raise this issue to google?
e.g. https://source.android.com/setup/contribute/report-bugs
> As the current stage3 tarballs for arm looks quite outdated
> (20161129), I expect that some efforts will be needed to roll it up to
> match the most up-to-date portage tree.
Please open a bug report to remind the ARM team to update stage3
tarballs.
Benda
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-05-02 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 16:31 [gentoo-soc] Weekly report 04/30 Pengcheng Xu
2018-05-02 9:21 ` Benda Xu [this message]
2018-05-05 18:34 ` Pengcheng Xu
2018-05-06 7:18 ` Benda Xu
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=87bmdyl8fw.fsf@gentoo.org \
--to=heroxbd@gentoo.org \
--cc=gentoo-soc@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox