From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>,
linux-fbdev@vger.kernel.org,
Thomas Winischhofer <thomas@winischhofer.net>,
Kees Cook <keescook@chromium.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Sami Tolvanen <samitolvanen@google.com>
Subject: Re: [PATCH 0/3] console: Expand dummy functions for CFI
Date: Wed, 28 Feb 2018 15:26:41 +0000 [thread overview]
Message-ID: <20180228152641.GA16045@kroah.com> (raw)
In-Reply-To: <2698133.VOZeH6rfJt@amdc3058>
On Wed, Feb 28, 2018 at 04:14:38PM +0100, Bartlomiej Zolnierkiewicz wrote:
> On Wednesday, February 28, 2018 04:09:47 PM Bartlomiej Zolnierkiewicz wrote:
> > On Monday, February 26, 2018 04:04:17 PM Kees Cook wrote:
> > > This is a small series that cleans up struct consw a bit and
> > > prepares it for Control Flow Integrity checking (i.e. Clang's
> > > -fsanitizeÏi).
> >
> > for drivers/video/ parts:
> >
> > Acked-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
>
> also I'll be happy to merge all patches through fbdev tree
> (if Greg is fine with it and ACKs drivers/usb/ parts)
I've already taken this through the tty tree, sorry about that.
Shouldn't cause any merge issues.
greg k-h
prev parent reply other threads:[~2018-02-28 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180227000432epcas2p1408299421426381f05a548283953b064@epcas2p1.samsung.com>
2018-02-27 0:04 ` [PATCH 0/3] console: Expand dummy functions for CFI Kees Cook
2018-02-27 0:04 ` [PATCH 1/3] console: SisUSB2VGA: Drop dummy con_font_get() Kees Cook
2018-02-27 0:04 ` [PATCH 2/3] console: Fill in struct consw argument names Kees Cook
2018-02-27 0:04 ` [PATCH 3/3] console: Expand dummy functions for CFI Kees Cook
2018-02-28 15:09 ` [PATCH 0/3] " Bartlomiej Zolnierkiewicz
2018-02-28 15:14 ` Bartlomiej Zolnierkiewicz
2018-02-28 15:26 ` Greg Kroah-Hartman [this message]
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=20180228152641.GA16045@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=keescook@chromium.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=samitolvanen@google.com \
--cc=thomas@winischhofer.net \
/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).