From: Viresh Kumar <viresh.kumar@...> commit deaa51465105a7eda19a627b10372f4f7c51a4df upstream. This patch adds debugfs support to OPP layer to export OPPs and their properties for all the

Testing git send-email ... please ignore.

Looks like this didn't hit the mailing list. I will resend again. Sorry for the noise. ChenYu

Hi all, Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today. *Please note that the IRC meeting was rescheduled to UTC (GMT) 09:00 starting

It sounds better to send a series with using these defines one time than separating it with defines and using codes with two times. I will send patch series later, thanks! Best regards, Johnson

For the TSN case I would say it is rather unlikely that this is already in use with any of our current CIP kernels. But I may miss earlier use cases besides TSN. For now, I would not invest

Hi! I did a bit of research on CVE-2020-10742. Unfortunately, RedHat is a bad player here, and bug reports are partly hidden from

Hi! I don't see anything wrong with the patch. OTOH I'd expect to see this in a series with the code actually using these defines. Is there a reason to merge it on its own? Best

Hi! Yes, IIRC. Ok, good to know. So... there are few reasons why it is important to know what is in use or not: 1) If we see patch in stable, how much effort should be spent reviewing it? 2) If

FYI Kind regards, Chris

From: Christina Quast <cquast@...> commit 7ebd1ea798a4932231b18499df136fb552f6f648 upstream. The values are extraced from the "AM335x SitaraTM Processors Technical Reference Manual",

Hi,

Hi! v4.4.225-cip45-rt29 should be available at kernel.org. Trees are available

Hi Iwamatsu-san,

commit 6f89dd9e9325d05b1f54d860dbbc84b42aa40759 upstream. The iwg20d comes with a 7" capacitive touch screen, therefore add support for it. Signed-off-by: Fabrizio Castro

Hi, Indeed, there is an overlapping property. I will post v2. Thank you for pointing that out. Marian

Hi,

Hi,

Hi,

Hello Kernel maintainers, I saw this warning [0] by chance this evening when doing a build with the moxa_mxc_defconfig [1] Kernel config. Is this something we want to