All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.11-rc5
Date: Mon, 25 Jan 2021 09:41:15 +0530	[thread overview]
Message-ID: <YA5E44s1zl4aCD6x@Gentoo> (raw)
In-Reply-To: <b975e215-0dd1-65fe-be51-c7c8c7b6571a@roeck-us.net>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8; format=flowed, Size: 2200 bytes --]

On 20:06 Sun 24 Jan 2021, Guenter Roeck wrote:
>On 1/24/21 7:56 PM, Bhaskar Chowdhury wrote:
>> On 19:48 Sun 24 Jan 2021, Guenter Roeck wrote:
>>> On Sun, Jan 24, 2021 at 05:06:40PM -0800, Linus Torvalds wrote:
>>>> So this rc looked fairly calm and small, all the way up until today.
>>>>
>>>> In fact, over 40% of the non-merge commits came in today, as people
>>>> unloaded their work for the week on me. The end result is a slightly
>>>> larger than usual rc5 (but both 5.10 and 5.8 were bigger, so not some
>>>> kind of odd outlier).
>>>>
>>>> Nothing particularly stands out. We had a couple of splice()
>>>> regressions that came in during the previous release as part of the
>>>> "get rid of set_fs()" development, but they were for odd cases that
>>>> most people would never notice. I think it's just that 5.10 is now
>>>> getting more widely deployed so people see the fallout from that
>>>> rather fundamental change in the last release.  And the only reason I
>>>> even reacted to those is just because I ended up being involved with
>>>> some of the tty patches during the early calm period of the past week.
>>>> There's a few more still pending.
>>>>
>>>> But the bulk of it all is all the usual miscellaneous fixes all over
>>>> the place, and a lot of it is truly trivial one- or few-liners. Just
>>>> under half the patch is for drivers, with the rest being the usual mix
>>>> of tooling, arch updates, filesystem and core (mm, scheduling,
>>>> networking).
>>>>
>>>> Nothing here makes me go "Uhhuh" in other words.
>>>>
>>>
>>> Looking pretty good now.
>>>
>>> Build results:
>>>     total: 153 pass: 153 fail: 0
>>> Qemu test results:
>>>     total: 430 pass: 430 fail: 0
>>>
>>> Guenter
>>
>> Hey,
>>
>> Mind letting us know ,what you are running? Any automated stuff? Any specific
>> tool or tools?? Scripts???
>>
>> Bloody curious to know Guenter ...if those stuff are expose able to public
>> consumption , please do provide the pointer too (I am being lazy to find it)
>>
>
>Results:
>	https://kerneltests.org/builders
>Script repository:
>	https://github.com/groeck/linux-build-test
>
>Guenter
>

Thanks a bunch!


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

  reply	other threads:[~2021-01-25  4:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-25  1:06 Linux 5.11-rc5 Linus Torvalds
2021-01-25  3:48 ` Guenter Roeck
2021-01-25  3:56   ` Bhaskar Chowdhury
2021-01-25  4:06     ` Guenter Roeck
2021-01-25  4:11       ` Bhaskar Chowdhury [this message]
2021-01-25 20:34 ` Chris Wilson
2021-01-25 20:49   ` Linus Torvalds
2021-01-25 21:33     ` Mike Rapoport
2021-01-25 21:46       ` Chris Wilson
2021-01-26  9:33         ` Chris Wilson
2021-01-26 16:24         ` Mike Rapoport
2021-01-26 18:45           ` Linus Torvalds
2021-01-27  9:38             ` Greg KH
2021-02-04 18:19     ` Mike Rapoport
2021-02-04 18:32       ` Linus Torvalds
2021-02-05  6:54         ` Greg KH
2021-01-25 21:04   ` Mike Rapoport
2021-01-25 21:13     ` Chris Wilson
2021-01-26 16:37       ` Mike Rapoport
2021-01-28 21:00       ` 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=YA5E44s1zl4aCD6x@Gentoo \
    --to=unixbhaskar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.