From: Joe Perches <joe@perches.com>
To: Kees Cook <keescook@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: BUG and WARN kernel log levels
Date: Wed, 17 Aug 2016 15:49:29 -0700 [thread overview]
Message-ID: <1471474169.4319.1.camel@perches.com> (raw)
In-Reply-To: <CAGXu5jLi_qnaGiykDrzaarJ2tDPQOyc3Aae0JBtGGMOZZaJ-qw@mail.gmail.com>
On Wed, 2016-08-17 at 14:19 -0700, Kees Cook wrote:
> On Wed, Aug 17, 2016 at 9:36 AM, Joe Perches <joe@perches.com> wrote:
[]
> > And here I submitted patches:
> > https://lkml.org/lkml/2010/10/30/176
> Ah, I see some of this series landed. I see commits scattered in the
> tree, but not as many as you sent, I think. What still remains?
No idea.
There wasn't any enthusiasm to apply the asm-generic
patch so I didn't push it.
prev parent reply other threads:[~2016-08-17 22:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 18:53 BUG and WARN kernel log levels Kees Cook
2016-08-15 19:00 ` Joe Perches
2016-08-15 20:28 ` Kees Cook
2016-08-15 20:39 ` Joe Perches
2016-08-17 16:36 ` Joe Perches
2016-08-17 21:19 ` Kees Cook
2016-08-17 22:49 ` Joe Perches [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=1471474169.4319.1.camel@perches.com \
--to=joe@perches.com \
--cc=keescook@google.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox