> From: Benda Xu <heroxbd@gentoo.org> 
> Sent: Wednesday, May 2, 2018 5:21 PM
> To: gentoo-soc@lists.gentoo.org
> Subject: Re: [gentoo-soc] Weekly report 04/30
> 
> Hi Pengcheng, 
> Looks good to me.  Looking forward to your UART and init hacks. 

The init hacks are in this week's work. I won't be able to get the
UART cable that my friend made until May 12th, though. I'll mention how
it goes when I get the cable, so stay tuned.

> "Pengcheng Xu" <mailto: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? 

I've linked the referred articles inline; is that not enough (and I need to
Explicitly list the references at the end of the article)?

> > 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

The problem is that I can't find a repository for angler's kernel source at
https://android.googlesource.com/ , and angler is approaching its EOL deadline;
what's more, the problems I encounter are located in the sources that are not
used by Android (they're off in the device defconfig). I'll try though, but I
don't expect much in this.
 
> > 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. 

Bug created, link: https://bugs.gentoo.org/654994 

> Benda 


-- 
Pengcheng Xu (KireinaHoro)
i@jsteward.moe