[Nexus 10 Original Android Development] Khaon:
Yes, I upload each time, most of the time, the lastest build after having boot with it.

However, they may not be stable. However, since the kernel is mature most of the time it is little update such syncing with f2fs,etc.

Release I make official on the topic

should be stable

1. No, cache should remain with the filesystem you choice. I don't think there is anything formating the cache to ext4. However if you take a look at the content of the cache partition, it is barely used, only by the system for a few files. /data is more used than /cache to do caching.

It is normal that system is ext4: for now building a rom make an image of the system partition. Thus its fs is determined by the buider. User can not (yet?) choose /system's fs. I could build an f2fs system image, would not require more compilation just rebuild the image but honestly since the system partition is read only, having ext4 on system is a overall a clever choice

2. Indeed you don't have really to trim your block device. F2FS supports real-time triming. As stated in f2fs doc the discard mount flag does the following:

discard Issue discard/TRIM commands when a segment is cleaned.

----------------------------------------------------------------------------------------------------

Well since everything seems to be smooth and stable here is the latest changelog:

kernel:

cpufreq:

cpufreq: Retain only online cpus in managed_policy->cpus

cpufreq:interactive:reworked tunnables

cpufreq:interactive: making sure cpufreq stays low when it needs to stay low

cpufreq:interactive:switched to touchboost driver

cpufreq: interactive: prevents the frequency to directly raise above the hispeed_freq from a lower frequency.

cpufreq: interactive: don't skip waking up speedchange_task if target_freq > policy->cur

cpufreq: interactive: delete timers for GOV_START

cpufreq: interactive: Fix null pointer dereference in interactive governor

cpufreq: interactive: Remove unnecessary cpu_online() check

cpufreq:ktoonservative:switch to generic input touchboost driver

Tweaks on OC (from [MENTION=4325945]ktoonsez[/MENTION] )

Makefile:

Makefile:removed graphite flags

exynos:

exynos:increased thermald throttling temp

drivers:

input: touchboost: add my generic touchboost driver governor agnostic. Its slightly changed from my N5, N4 and N7 version to adapt to this arch ( from [MENTION=3292224]franciscofranco[/MENTION] )

filesystems:

f2fs:sync with upstream branch

frandom: A fast random number generator

block:

block:bfq:adjusted tunnables for nand devices

block:bfq v7r7 v7r7: . BUGFIX: Prevent the OOM queue from being involved in the queue cooperation mechanism. In fact, since the requests temporarily redirected to the OOM queue could be redirected again to dedicated queues at any time, the state needed to correctly handle merging with the OOM queue would be quite complex and expensive to maintain. Besides, in such a critical condition as an out of memory, the benefits of queue merging may be little relevant, or even negligible. . IMPROVEMENT: Let the OOM queue be initialized only once. Previously, the OOM queue was reinitialized, at each request enqueue, with the parameters related to the process that issued that request. Depending on the parameters of the processes doing I/O, this could easily cause the OOM queue to be moved continuously across service trees, or even across groups. It also caused the parameters of the OOM queue to be continuously reset in any case. . CODE IMPROVEMENT. Performed some minor code cleanups, and added some BUG_ON()s that, if the weight of an entity becomes inconsistent, should better help understand why.

kernel:

sched: LOAD_FREQ (4*HZ+61) avoids loadavg Moire. From http://ripke.com/loadavg/moire

Merge remote-tracking branch 'common/android-3.4' into khaon-new

Rom:

build:use a modular list to disable O3 optimizations (fixes for example blue tooth crashes, report any new other FC's, if they related to the optimizations flags, I can try tracking down the relevant module and add it to the list.

audio_effects:added support for viper4audio

power: removed touch screen boost's code because we use kernel side touch boost driver