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

Hello Ben, Thanks again for your detailed reviews. I have fixed the tags patch with your suggestions. I will reply to them separately. [cip-kernel-sec][RESEND v2 1/2] report_affected: add support

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

Hi, Agree. We think that we need to add the following sentences. --- We do not apply patches that have not been applied to upstream (Linus

I've implemented that option. I hadn't thought of that, but it does seem possible. However, I think that rather than editing a generated list it would be better to have a separate manually

I've applied patches 1, 2, 3, and 5 (as it didn't depend on 4). Please re-send the remaining two with my requested changes. Ben. -- Ben Hutchings, Software Developer

Ben Hutchings pushed to branch masterat cip-project / cip-kernel / cip-kernel-secCommits: 6b530a7c by Daniel Sangorrinat 2019-07-10T14:43:03Zcheck_git_repo: add checks to the local repositoryAdd

On Wed, 2019-07-10 at 10:24 +0900, Daniel Sangorrin wrote: [...] > --- a/scripts/report_affected.py > +++ b/scripts/report_affected.py [...] > @@ -22,15 +24,47 @@ def main(git_repo, remotes, > if