3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
commit 43cdd1b716b26f6af16da4e145b6578f98798bf6 upstream.
There's no need to be printing a raw kernel pointer to the kernel log at
every boot.
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
commit 43cdd1b716b26f6af16da4e145b6578f98798bf6 upstream.
There's no need to be printing a raw kernel pointer to the kernel log at
every boot. So just remove it, and
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
commit 43cdd1b716b26f6af16da4e145b6578f98798bf6 upstream.
There's no need to be printing a raw kernel pointer to the kernel log at
every boot.
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
commit 43cdd1b716b26f6af16da4e145b6578f98798bf6 upstream.
There's no need to be printing a raw kernel pointer to the kernel log at
every boot. So just remove it, and
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
commit 43cdd1b716b26f6af16da4e145b6578f98798bf6 upstream.
There's no need to be printing a raw kernel pointer to the kernel log at
every boot.
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
commit 43cdd1b716b26f6af16da4e145b6578f98798bf6 upstream.
There's no need to be printing a raw kernel pointer to the kernel log at
every boot. So just remove it, and
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
commit 43cdd1b716b26f6af16da4e145b6578f98798bf6 upstream.
There's no need to be printing a raw kernel pointer to the kernel log at
every boot.
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
commit 43cdd1b716b26f6af16da4e145b6578f98798bf6 upstream.
There's no need to be printing a raw kernel pointer to the kernel log at
every boot. So just remove it, and change
4.15-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
commit 43cdd1b716b26f6af16da4e145b6578f98798bf6 upstream.
There's no need to be printing a raw kernel pointer to the kernel log at
every boot.
4.15-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
commit 43cdd1b716b26f6af16da4e145b6578f98798bf6 upstream.
There's no need to be printing a raw kernel pointer to the kernel log at
every boot. So just remove it, and
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
commit 43cdd1b716b26f6af16da4e145b6578f98798bf6 upstream.
There's no need to be printing a raw kernel pointer to the kernel log at
every boot.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
commit 43cdd1b716b26f6af16da4e145b6578f98798bf6 upstream.
There's no need to be printing a raw kernel pointer to the kernel log at
every boot. So just remove it, and
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
commit 43cdd1b716b26f6af16da4e145b6578f98798bf6 upstream.
There's no need to be printing a raw kernel pointer to the kernel log at
every boot.
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
commit 43cdd1b716b26f6af16da4e145b6578f98798bf6 upstream.
There's no need to be printing a raw kernel pointer to the kernel log at
every boot. So just remove it, and change
On Mon, Jan 22, 2018 at 11:19:36AM +0800, wang_q...@venustech.com.cn wrote:
>
> I has recvied a cve-id from mitre.org for this security bug .
> should this cve-id( CVE-2018-5750) be mentioned in kernel change log?
Only if Rafael wants to hand-edit the patch, it's not really needed for
a kernel
On Mon, Jan 22, 2018 at 11:19:36AM +0800, wang_q...@venustech.com.cn wrote:
>
> I has recvied a cve-id from mitre.org for this security bug .
> should this cve-id( CVE-2018-5750) be mentioned in kernel change log?
Only if Rafael wants to hand-edit the patch, it's not really needed for
a kernel
On Sat, Jan 20, 2018 at 09:03:33AM +0100, Rafael J. Wysocki wrote:
> On Sat, Jan 20, 2018 at 8:36 AM, Greg Kroah-Hartman
> wrote:
> > On Sat, Jan 20, 2018 at 12:53:39AM +0100, Rafael J. Wysocki wrote:
> >> On Fri, Jan 19, 2018 at 10:06 AM, Greg Kroah-Hartman
> >>
On Sat, Jan 20, 2018 at 09:03:33AM +0100, Rafael J. Wysocki wrote:
> On Sat, Jan 20, 2018 at 8:36 AM, Greg Kroah-Hartman
> wrote:
> > On Sat, Jan 20, 2018 at 12:53:39AM +0100, Rafael J. Wysocki wrote:
> >> On Fri, Jan 19, 2018 at 10:06 AM, Greg Kroah-Hartman
> >> wrote:
> >> > There's no need to
On Sat, Jan 20, 2018 at 8:36 AM, Greg Kroah-Hartman
wrote:
> On Sat, Jan 20, 2018 at 12:53:39AM +0100, Rafael J. Wysocki wrote:
>> On Fri, Jan 19, 2018 at 10:06 AM, Greg Kroah-Hartman
>> wrote:
>> > There's no need to be printing a raw
On Sat, Jan 20, 2018 at 8:36 AM, Greg Kroah-Hartman
wrote:
> On Sat, Jan 20, 2018 at 12:53:39AM +0100, Rafael J. Wysocki wrote:
>> On Fri, Jan 19, 2018 at 10:06 AM, Greg Kroah-Hartman
>> wrote:
>> > There's no need to be printing a raw kernel pointer to the kernel log at
>> > every boot. So
On Sat, Jan 20, 2018 at 12:53:39AM +0100, Rafael J. Wysocki wrote:
> On Fri, Jan 19, 2018 at 10:06 AM, Greg Kroah-Hartman
> wrote:
> > There's no need to be printing a raw kernel pointer to the kernel log at
> > every boot. So just remove it, and change the whole
On Sat, Jan 20, 2018 at 12:53:39AM +0100, Rafael J. Wysocki wrote:
> On Fri, Jan 19, 2018 at 10:06 AM, Greg Kroah-Hartman
> wrote:
> > There's no need to be printing a raw kernel pointer to the kernel log at
> > every boot. So just remove it, and change the whole message to use the
> > correct
On Fri, Jan 19, 2018 at 10:06 AM, Greg Kroah-Hartman
wrote:
> There's no need to be printing a raw kernel pointer to the kernel log at
> every boot. So just remove it, and change the whole message to use the
> correct dev_info() call at the same time.
>
> Reported-by:
On Fri, Jan 19, 2018 at 10:06 AM, Greg Kroah-Hartman
wrote:
> There's no need to be printing a raw kernel pointer to the kernel log at
> every boot. So just remove it, and change the whole message to use the
> correct dev_info() call at the same time.
>
> Reported-by: Wang Qize
> Cc: stable
I
There's no need to be printing a raw kernel pointer to the kernel log at
every boot. So just remove it, and change the whole message to use the
correct dev_info() call at the same time.
Reported-by: Wang Qize
Cc: stable
Signed-off-by: Greg
There's no need to be printing a raw kernel pointer to the kernel log at
every boot. So just remove it, and change the whole message to use the
correct dev_info() call at the same time.
Reported-by: Wang Qize
Cc: stable
Signed-off-by: Greg Kroah-Hartman
diff --git a/drivers/acpi/sbshc.c
26 matches
Mail list logo