linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kris Chaplin <kris.chaplin@amd.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Michal Simek <michal.simek@amd.com>
Subject: Re: Reg the next LTS kernel (6.1?)
Date: Thu, 12 Jan 2023 12:23:46 +0000	[thread overview]
Message-ID: <c6c4787f-f0c6-7285-f782-d36bd86b1e01@amd.com> (raw)
In-Reply-To: <Y53BputYK+3djDME@kroah.com>

Hello Greg,

> You tell me please.  How has your testing gone for 6.1 so far?  Does it
> work properly for you?  Are you and/or your company willing to test out
> the -rc releases and provide feedback if it works or not for your
> systems?  Do you have problems with 6.1.y vs. older kernels?  Is there
> anything missing in it that you feel needs to be addressed with a newer
> kernel instead?

We have been integrating and testing 6.1 on the Microblaze, ARM32 and
ARM64-bit architectures over the past few weeks.  These builds have
been successful and we are able to run our regression tests on hardware
targeting our FPGA SoC devices.

We're continuing our tests as new updates to the 6.1 kernel series
appear.

Hope that information is of use.
Kris Chaplin - Xilinx/AMD


  parent reply	other threads:[~2023-01-12 12:24 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-07  7:37 Reg the next LTS kernel (6.1?) Kaiwan N Billimoria
2022-10-07  7:46 ` Greg KH
2022-10-07  7:50   ` Kaiwan N Billimoria
2022-12-17 13:02     ` Kaiwan N Billimoria
2022-12-17 13:18       ` Greg KH
2022-12-17 13:44         ` Kaiwan N Billimoria
2022-12-17 16:40           ` Willy Tarreau
2022-12-20  1:45             ` Kaiwan N Billimoria
2022-12-18  8:42           ` Greg KH
2023-01-11  8:15         ` Conor Dooley
2023-01-11 11:33           ` Greg KH
2023-01-11 19:05             ` Conor Dooley
2023-01-12 12:23         ` Kris Chaplin [this message]
2023-01-12 12:26           ` Michal Simek
2023-01-13 11:27             ` Greg KH
2023-01-13 12:54               ` Michal Simek
2023-01-13 16:22                 ` Greg KH
2023-01-13 21:40                   ` Theodore Ts'o
2023-01-14  7:14                     ` Willy Tarreau
2023-01-14  8:26                       ` Greg KH
2023-01-14  8:47                         ` Willy Tarreau
2023-02-05  6:27                         ` Ruslan Bilovol
2023-02-16 10:41                           ` Kris Chaplin
2023-02-16 11:20                             ` Greg KH
2023-02-16 11:23                               ` Kris Chaplin
2023-01-16 12:16                     ` Michal Simek
2023-01-17  3:07                       ` Theodore Ts'o
2023-01-16 12:02                   ` Michal Simek
2023-01-13 11:24           ` Greg KH
2022-10-07 15:04 Carl Dasantas
2022-10-07 15:36 ` Greg KH
2022-10-07 16:07   ` Carl Dasantas
2022-10-07 16:34     ` Greg KH
2022-10-07 19:50     ` Theodore Ts'o
2022-10-07 17:37 ` Slade Watkins

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=c6c4787f-f0c6-7285-f782-d36bd86b1e01@amd.com \
    --to=kris.chaplin@amd.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@amd.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;
as well as URLs for NNTP newsgroup(s).