All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <shuah.kh@samsung.com>
To: "Bird, Tim" <Tim.Bird@sonymobile.com>,
	"ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Shuah Khan <shuah.kh@samsung.com>
Subject: Re: [Ksummit-discuss] kselftest - What's in 3.17 and plans for 3.18 and beyond
Date: Thu, 07 Aug 2014 13:59:39 -0600	[thread overview]
Message-ID: <53E3DAAB.7000406@samsung.com> (raw)
In-Reply-To: <F5184659D418E34EA12B1903EE5EF5FD0130D4AC5B84@seldmbx02.corpusers.net>

On 08/07/2014 12:24 PM, Bird, Tim wrote:
>
> I'm quite interested in this (as is the CEWG), and I have lots of questions.
> Will this be discussed/presented at KS or LinuxCon?  Should I ask my
> questions on this list or wait until Chicago?  Are there any LKML threads
> with info I can look at in the meantime?
>
> Thanks.  This sounds like great work.

The plan to discuss this at the KS. Please continue this thread with
questions you have. I can point you to links to the patches for the
work done so far in 3.17 if you are interested.

-- Shuah

-- 
Shuah Khan
Senior Linux Kernel Developer - Open Source Group
Samsung Research America(Silicon Valley)
shuah.kh@samsung.com | (970) 672-0658

  reply	other threads:[~2014-08-07 19:59 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-07 14:36 [Ksummit-discuss] kselftest - What's in 3.17 and plans for 3.18 and beyond Shuah Khan
2014-08-07 18:24 ` Bird, Tim
2014-08-07 19:59   ` Shuah Khan [this message]
2014-08-08  2:18 ` Masami Hiramatsu
2014-08-11 14:11   ` Shuah Khan
2014-08-11 16:13     ` Masami Hiramatsu
2014-08-12 13:00       ` Grant Likely
2014-08-12 16:15         ` Guenter Roeck
2014-08-12 16:21           ` Masami Hiramatsu
2014-08-12 16:51             ` Geert Uytterhoeven
2014-08-12 17:15             ` Theodore Ts'o
2014-08-12 16:23           ` Grant Likely
2014-08-12 16:49             ` Mark Brown
2014-08-13  6:26               ` Grant Likely
2014-08-13 10:40                 ` Mark Brown
2014-08-13 11:12                   ` Geert Uytterhoeven
2014-08-13 12:42                     ` Mark Brown
2014-08-13 13:08                       ` Geert Uytterhoeven
2014-08-13 15:00                   ` Kevin Hilman
2014-08-13 16:40                     ` Olof Johansson
2014-08-13 17:11                       ` Mark Brown
2014-08-12 17:46             ` Tim Bird
2014-08-12 18:06               ` Steven Rostedt
2014-08-12 20:52                 ` Tim Bird
2014-08-14 16:35                 ` Grant Likely
2014-08-12 17:30           ` Andy Lutomirski
2014-08-12 16:34         ` Shuah Khan
2014-08-13  8:35         ` Linus Walleij
2014-08-13 16:11           ` Guenter Roeck
2014-08-13 16:16             ` Andy Lutomirski
2014-08-13 16:44               ` Bird, Tim
2014-08-13 17:07                 ` Grant Likely
2014-08-13 17:10                   ` Andy Lutomirski
2014-08-13 17:10                 ` Guenter Roeck
2014-08-18  3:10               ` Rob Landley
2014-08-18  3:08             ` Rob Landley
2014-08-18  7:16               ` Geert Uytterhoeven
2014-08-13 16:45           ` Masami Hiramatsu
2014-08-18  3:18             ` Rob Landley
2014-08-13 15:06         ` Aneesh Kumar K.V

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=53E3DAAB.7000406@samsung.com \
    --to=shuah.kh@samsung.com \
    --cc=Tim.Bird@sonymobile.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ksummit-discuss@lists.linuxfoundation.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 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.