Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Thu, 13 Feb 2020 02:47:30 +0530
From:   Jeffrin Jose <jeffrin@rajagiritech.edu.in>
To:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc:     linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
        akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
        patches@kernelci.org, ben.hutchings@codethink.co.uk,
        lkft-triage@lists.linaro.org, stable@vger.kernel.org,
        jeffrin@rajagiritech.edu.in
Subject: Re: [PATCH 5.4 000/309] 5.4.19-stable review
Message-ID: <20200212211730.GA36144@debian>
References: <20200210122406.106356946@linuxfoundation.org>
 <20200212073531.GA5184@debian>
 <20200212133037.GA1791775@kroah.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200212133037.GA1791775@kroah.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Wed, Feb 12, 2020 at 05:30:37AM -0800, Greg Kroah-Hartman wrote:
> On Wed, Feb 12, 2020 at 01:05:31PM +0530, Jeffrin Jose wrote:
> > On Mon, Feb 10, 2020 at 04:29:16AM -0800, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 5.4.19 release.
> > > There are 309 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 Wed, 12 Feb 2020 12:18:57 +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/v5.x/stable-review/patch-5.4.19-rc1.gz
> > > or in the git tree and branch at:
> > > 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.4.y
> > > and the diffstat can be found below.
> > 
> > hello ,
> > 
> > compiled and booted 5.4.19-rc1+ . No new error according to "sudo dmesg -l err"
> 
> Thanks for testing, there shouldn't be a need to run 'sudo' for that
> dmesg command :)
> 
> greg k-h

hello,

   thanks for helping me improve.
   i had "CONFIG_SECURITY_DMESG_RESTRICT=y"
   i did related to "sudo sysctl kernel.dmesg_restrict=0"
   now dmesg without sudo is working.

--
software engineer
rajagiri school of engineering and technology