linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Takeshi Ogasawara <takeshi.ogasawara@futuring-girl.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	 linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	 akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
	 patches@kernelci.org, lkft-triage@lists.linaro.org,
	pavel@denx.de,  jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com,  srw@sladewatkins.net,
	rwarsow@gmx.de, conor@kernel.org, allen.lkml@gmail.com
Subject: Re: [PATCH 6.6 000/580] 6.6.14-rc2 review
Date: Wed, 24 Jan 2024 20:58:26 +0900	[thread overview]
Message-ID: <CAKL4bV5AXGh4DD8fBjYF1gCuFcKTSYcXxdg1wh_1OsorV-TqZg@mail.gmail.com> (raw)
In-Reply-To: <20240123174533.427864181@linuxfoundation.org>

Hi Greg

On Wed, Jan 24, 2024 at 2:47 AM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> This is the start of the stable review cycle for the 6.6.14 release.
> There are 580 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Thu, 25 Jan 2024 17:44:18 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
>         https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.6.14-rc2.gz
> or in the git tree and branch at:
>         git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.6.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>

6.6.14-rc2 tested.

Build successfully completed.
Boot successfully completed.
No dmesg regressions.
Video output normal.
Sound output normal.

Lenovo ThinkPad X1 Carbon Gen10(Intel i7-1260P(x86_64) arch linux)

[    0.000000] Linux version 6.6.14-rc2rv
(takeshi@ThinkPadX1Gen10J0764) (gcc (GCC) 13.2.1 20230801, GNU ld (GNU
Binutils) 2.41.0) #1 SMP PREEMPT_DYNAMIC Wed Jan 24 20:06:42 JST 2024

Thanks

Tested-by: Takeshi Ogasawara <takeshi.ogasawara@futuring-girl.com>

  parent reply	other threads:[~2024-01-24 11:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23 17:47 [PATCH 6.6 000/580] 6.6.14-rc2 review Greg Kroah-Hartman
2024-01-23 20:22 ` SeongJae Park
2024-01-24  0:21 ` Kelsey Steele
2024-01-24  0:59 ` Luna Jernberg
2024-01-24  6:09 ` Bagas Sanjaya
2024-01-24  8:00 ` Ron Economos
2024-01-24  9:16 ` Conor Dooley
2024-01-24 10:23 ` Jon Hunter
2024-01-24 11:58 ` Takeshi Ogasawara [this message]
2024-01-24 13:23 ` Naresh Kamboju
2024-01-24 17:27 ` Florian Fainelli
2024-01-24 20:18 ` Shreeya Patel
2024-01-25 16:48 ` Miguel Ojeda

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=CAKL4bV5AXGh4DD8fBjYF1gCuFcKTSYcXxdg1wh_1OsorV-TqZg@mail.gmail.com \
    --to=takeshi.ogasawara@futuring-girl.com \
    --cc=akpm@linux-foundation.org \
    --cc=allen.lkml@gmail.com \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.org \
    /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).