public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: cip-dev@lists.cip-project.org
Cc: jan.kiszka@siemens.com
Subject: Re: [cip-dev] Starting 4.4 backports
Date: Wed, 16 Mar 2022 21:48:09 +0100	[thread overview]
Message-ID: <20220316204809.GA23976@duo.ucw.cz> (raw)
In-Reply-To: <16DCA3473A223E6A.28363@lists.cip-project.org>

[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]

Hi!

> So... I have some scripts, and I went through 4.9.299... I guess I
> could try to update linux-4.4.y tree with patches from 4.9.299.
> 
> I would not mind someone looking at notes I've made so far. They are
> at:
> 
> https://gitlab.com/cip-project/cip-kernel/lts-commit-list/-/blob/master/v4.4.org
> 
> There are some notes at begining of file explaining what different
> values of the first field are. Most important now is number -- it
> means that the patch looks "not worth the effort dealing with", and I
> plan to simply ignore it.
> 
> Comments? Is it okay to go ahead?

I have merged 4.9.299 changes with -cip, and result is at

https://gitlab.com/cip-project/cip-kernel/linux-cip/tree/ci/pavel/linux-test

. If there are no other comments, I'll push that as linux-4.4.y-cip on
kernel.org and I'll push the tree with just the changes from stable as
linux-4.4.y-st there, too.

I guess at some point we'll need to decide how to mark versions in the
linux-4.4.y-st tree. I guess we could use "-stX" as an extra
version. If we wait a bit, we can use X=Y-300 for corresponding 4.9.Y
version.

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

           reply	other threads:[~2022-03-16 20:48 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <16DCA3473A223E6A.28363@lists.cip-project.org>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220316204809.GA23976@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=cip-dev@lists.cip-project.org \
    --cc=jan.kiszka@siemens.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox