All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: "Linux Fbdev development list" <linux-fbdev@vger.kernel.org>,
	"Kyungtae Kim" <kt0755@gmail.com>,
	"Anthony Liguori" <aliguori@amazon.com>,
	b.zolnierkie@samsung.com,
	"Linux kernel mailing list" <linux-kernel@vger.kernel.org>,
	"DRI devel" <dri-devel@lists.freedesktop.org>,
	"Srivatsa S. Bhat" <srivatsa@csail.mit.edu>,
	"Solar Designer" <solar@openwall.com>,
	"Yang Yingliang" <yangyingliang@huawei.com>,
	xiao.zhang@windriver.com,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	张云海 <zhangyunhai@nsfocus.com>
Subject: Re: [PATCH] vgacon: fix out of bounds write to the scrollback buffer
Date: Mon, 03 Aug 2020 08:18:23 +0000	[thread overview]
Message-ID: <20200803081823.GD493272@kroah.com> (raw)
In-Reply-To: <9386c640-34dd-0a50-5694-4f87cc600e0f@kernel.org>

On Mon, Aug 03, 2020 at 10:08:43AM +0200, Jiri Slaby wrote:
> Hi,
> 
> On 31. 07. 20, 7:22, 张云海 wrote:
> > Remove whitespace at EOL
> 
> I am fine with the patch. However it should be sent properly (inline
> mail, having a PATCH subject etc. -- see
> Documentation/process/submitting-patches.rst). git send-email after git
> format-patch handles most of it.
> 
> There is also question who is willing to take it?
> 
> Bart? Greg? Should we route it via akpm, or will you Linus directly? (I
> can sign off and resend the patch which was attached to the mail I am
> replying to too, if need be.)

I can take it, if Bart can't, just let me know.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: "Linux Fbdev development list" <linux-fbdev@vger.kernel.org>,
	"Kyungtae Kim" <kt0755@gmail.com>,
	"Anthony Liguori" <aliguori@amazon.com>,
	b.zolnierkie@samsung.com,
	"Linux kernel mailing list" <linux-kernel@vger.kernel.org>,
	"DRI devel" <dri-devel@lists.freedesktop.org>,
	"Srivatsa S. Bhat" <srivatsa@csail.mit.edu>,
	"Solar Designer" <solar@openwall.com>,
	"Yang Yingliang" <yangyingliang@huawei.com>,
	xiao.zhang@windriver.com,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	张云海 <zhangyunhai@nsfocus.com>
Subject: Re: [PATCH] vgacon: fix out of bounds write to the scrollback buffer
Date: Mon, 3 Aug 2020 10:18:23 +0200	[thread overview]
Message-ID: <20200803081823.GD493272@kroah.com> (raw)
In-Reply-To: <9386c640-34dd-0a50-5694-4f87cc600e0f@kernel.org>

On Mon, Aug 03, 2020 at 10:08:43AM +0200, Jiri Slaby wrote:
> Hi,
> 
> On 31. 07. 20, 7:22, 张云海 wrote:
> > Remove whitespace at EOL
> 
> I am fine with the patch. However it should be sent properly (inline
> mail, having a PATCH subject etc. -- see
> Documentation/process/submitting-patches.rst). git send-email after git
> format-patch handles most of it.
> 
> There is also question who is willing to take it?
> 
> Bart? Greg? Should we route it via akpm, or will you Linus directly? (I
> can sign off and resend the patch which was attached to the mail I am
> replying to too, if need be.)

I can take it, if Bart can't, just let me know.

thanks,

greg k-h
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: 张云海 <zhangyunhai@nsfocus.com>,
	"Solar Designer" <solar@openwall.com>,
	b.zolnierkie@samsung.com,
	"Yang Yingliang" <yangyingliang@huawei.com>,
	"Kyungtae Kim" <kt0755@gmail.com>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Srivatsa S. Bhat" <srivatsa@csail.mit.edu>,
	"Anthony Liguori" <aliguori@amazon.com>,
	xiao.zhang@windriver.com,
	"DRI devel" <dri-devel@lists.freedesktop.org>,
	"Linux Fbdev development list" <linux-fbdev@vger.kernel.org>,
	"Linux kernel mailing list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] vgacon: fix out of bounds write to the scrollback buffer
Date: Mon, 3 Aug 2020 10:18:23 +0200	[thread overview]
Message-ID: <20200803081823.GD493272@kroah.com> (raw)
In-Reply-To: <9386c640-34dd-0a50-5694-4f87cc600e0f@kernel.org>

On Mon, Aug 03, 2020 at 10:08:43AM +0200, Jiri Slaby wrote:
> Hi,
> 
> On 31. 07. 20, 7:22, 张云海 wrote:
> > Remove whitespace at EOL
> 
> I am fine with the patch. However it should be sent properly (inline
> mail, having a PATCH subject etc. -- see
> Documentation/process/submitting-patches.rst). git send-email after git
> format-patch handles most of it.
> 
> There is also question who is willing to take it?
> 
> Bart? Greg? Should we route it via akpm, or will you Linus directly? (I
> can sign off and resend the patch which was attached to the mail I am
> replying to too, if need be.)

I can take it, if Bart can't, just let me know.

thanks,

greg k-h

  reply	other threads:[~2020-08-03  8:18 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200729130710.GA13262@openwall.com>
     [not found] ` <b764c575-70be-80dd-6718-e84370a7b2b3@nsfocus.com>
2020-07-30  6:46   ` [PATCH] vgacon: fix out of bounds write to the scrollback buffer Jiri Slaby
2020-07-30  6:46     ` Jiri Slaby
2020-07-30  6:46     ` Jiri Slaby
2020-07-30  7:38     ` Jiri Slaby
2020-07-30  7:38       ` Jiri Slaby
2020-07-30  7:38       ` Jiri Slaby
2020-07-30 10:39     ` 张云海
2020-07-30 10:39       ` 张云海
2020-07-30 10:39       ` 张云海
2020-07-31  5:22       ` 张云海
2020-07-31  5:22         ` 张云海
2020-07-31  5:22         ` 张云海
2020-08-03  8:08         ` Jiri Slaby
2020-08-03  8:08           ` Jiri Slaby
2020-08-03  8:08           ` Jiri Slaby
2020-08-03  8:18           ` Greg KH [this message]
2020-08-03  8:18             ` Greg KH
2020-08-03  8:18             ` Greg KH
2020-08-03  8:45             ` Daniel Vetter
2020-08-03  8:45               ` Daniel Vetter
2020-08-03  8:45               ` Daniel Vetter
2020-08-03  9:47               ` Greg KH
2020-08-03  9:47                 ` Greg KH
2020-08-03  9:47                 ` Greg KH
2020-08-03 11:07                 ` Bartlomiej Zolnierkiewicz
2020-08-03 11:07                   ` Bartlomiej Zolnierkiewicz
2020-08-03 11:07                   ` Bartlomiej Zolnierkiewicz
2020-08-04  7:37           ` Greg KH
2020-08-04  7:37             ` Greg KH
2020-08-04  7:37             ` Greg KH
     [not found] <CGME20200729070257eucas1p1f5841756104301e67907136e45d6e9f5@eucas1p1.samsung.com>
2020-07-29  7:02 ` Jiri Slaby
2020-07-29  7:02   ` Jiri Slaby
2020-07-29  7:02   ` Jiri Slaby
2020-07-29  7:53   ` 张云海
2020-07-29  7:53     ` 张云海
2020-07-29  7:53     ` 张云海
2020-07-29  8:11     ` Jiri Slaby
2020-07-29  8:11       ` Jiri Slaby
2020-07-29  8:11       ` Jiri Slaby
2020-07-29  8:19       ` 张云海
2020-07-29  8:19         ` 张云海
2020-07-29  8:19         ` 张云海
2020-07-29 11:20         ` Jiri Slaby
2020-07-29 11:20           ` Jiri Slaby
2020-07-29 11:20           ` Jiri Slaby
2020-07-29 13:37   ` Bartlomiej Zolnierkiewicz
2020-07-29 13:37     ` Bartlomiej Zolnierkiewicz
2020-07-29 13:37     ` Bartlomiej Zolnierkiewicz

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=20200803081823.GD493272@kroah.com \
    --to=greg@kroah.com \
    --cc=aliguori@amazon.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jirislaby@kernel.org \
    --cc=kt0755@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=solar@openwall.com \
    --cc=srivatsa@csail.mit.edu \
    --cc=torvalds@linux-foundation.org \
    --cc=xiao.zhang@windriver.com \
    --cc=yangyingliang@huawei.com \
    --cc=zhangyunhai@nsfocus.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 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.