On Thu, 2019-07-11 at 18:51 +0200, Jan Kiszka wrote: [...] > > 4.19/arm/hitachi_omap_defconfig > > 4.19/arm/moxa_mxc_defconfig > > 4.19/arm/siemens_am335x-axm2_defconfig > >

Hi all, CIP kernel team has released Linux kernel 4.19.58-cip6 and 4.4.185-cip35. Linux-4.19.y-cip has been updated from base version from 4.19.56 to 4.19.58, and linux-4.4.y-cip has been updated

Hi All, RTC PCF85263 is used by iWave RZ/G1C SBC( iwg23s) platform. We have upstreamed this driver support on 4.19 kernel [1] [1].

Hello Ben, [Note] repeating the reply because I got some rejected mails. You can discard the 4.4 old configurations from Toshiba. At the moment, we only need support for this

Hi! I went ahead, and applied this to linux-4.19.y-cip-rt-rebase branch, too. If it is easy to add that one to testing, it would be nice. Best regards, Pavel -- (english)

Thanks, applied to 4.4-cip, and pushed out. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Hi! Thanks, applied and pushed out. Sorry for the delay. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures)

Hi Pavel, Is there a chance to update 4.4-rt based on Daniel' 4.4.179-rt181 release, but then to 4.4.182 in order to have SACK fixes in? Thanks, Jan PS: Please make it -rt24 then. ;) -- Siemens

Hi, Oh, I missed the sentence. Thank you very much for telling it. Is the backporting limited to the supported hardware? Best regards, Hiraku Toyooka 2019年7月11日(木) 8:47

Although the README already contains all the information that users may need, there are some bits of know-how that are better expressed through a step-by-step quickstart or tutorial. This files tries

Hello Ben, Sorry, I realized that there were a few issues in the Quickstart so I am resending the patch. Please ignore the previous one. [cip-kernel-sec][Quickstart v2] docs: add a quickstart with

Probably this should be squashed into the corresponding patches. Signed-off-by: Daniel Sangorrin <daniel.sangorrin@...> --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1

Although the README already contains all the information that users may need, there are some bits of know-how that are better expressed through a step-by-step quickstart or tutorial. This files tries

Hello Ben, I was planning to put this into the CIP wiki, but I though it might be better to store it together with the source code so there you go. [cip-kernel-sec][quickstart] docs: add a

Reporting on tags is useful for product engineers that have shipped a kernel with a specific tag and need to know which issues affect their product after some time. Examples: $

Hello Ben, I think this should be fine. You need to remove the cached file import/stable_branches.yml [cip-kernel-sec][RESEND v3] report_affected: add support for To be honest, I am not 100% sure

Sorry, I went too fast. I should have moved the regexp to get_base_ver_stable_branch. I will resend. Thanks, Daniel

[...] Thanks, you are right. I have used re.escape('.'). I didn't know this function, it's really useful not having to remember how to escape characters (I figured out I could have used \\.). I think

Rather than looking up each issue file, I would like to have an overview of what each CVE ID means. Example: $ ./scripts/report_affected.py --show-description linux-4.4.y-cip Signed-off-by: Daniel

Reporting on tags is useful for product engineers that have shipped a kernel with a specific tag and need to know which issues affect their product after some time. Examples: $