public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Ulrich Hecht <uli@fpond.eu>
Cc: "pavel@denx.de" <pavel@denx.de>,
	"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: Re: Request for reviews for 4.4-st44 4.4-cip79
Date: Mon, 4 Sep 2023 12:42:07 +0200	[thread overview]
Message-ID: <ZPW0f+krBDyMzAQB@duo.ucw.cz> (raw)
In-Reply-To: <1583308606.3395319.1693820637255@webmail.strato.com>

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

Hi!

> Here are the manual backports for the upcoming 4.4-st44 and 4.4-cip79 releases that should be reviewed, and that can currently be found in
> https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.4.y-st-rc
> 
> My apologies, this is a big one. Thankfully, most backports are of the trivial sort:

Ok, let me take a look.

> There is also "x86/msr-index: remove duplicate definition of
>MSR_AMD64_DE_CFG", a minor fixup for a warning introduced in the
>previous release.

I'd do this one the other way around -- keep the definition in the
header, as we have in mainline, and remove the one in the .c file.

Best regards,
								Pavel

-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

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

  reply	other threads:[~2023-09-04 10:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-04  9:43 Request for reviews for 4.4-st44 4.4-cip79 Ulrich Hecht
2023-09-04 10:42 ` Pavel Machek [this message]
2023-09-04 11:43 ` Pavel Machek
2023-09-06  8:32   ` [cip-dev] " Ulrich Hecht
2023-09-11  8:27     ` Pavel Machek

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=ZPW0f+krBDyMzAQB@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=cip-dev@lists.cip-project.org \
    --cc=uli@fpond.eu \
    /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