ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Tanish Shinde <tanishshinde2006@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	"ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Anatomy Of The Linux Kernel
Date: Mon, 3 Jun 2019 07:48:09 +0300	[thread overview]
Message-ID: <20190603044809.GF5261@mtr-leonro.mtl.com> (raw)
In-Reply-To: <CAFTVhMen6LqB2p8Ptq0CeUWw9hiJDVU6Z_70yMbQLSG2HbJVOQ@mail.gmail.com>

On Sat, Jun 01, 2019 at 11:22:32PM +0530, Tanish Shinde wrote:
> On Sat, 1 Jun 2019 at 10:26 PM, Tanish Shinde <tanishshinde2006@gmail.com>
> wrote:
>
> > hi
> > I understand that you think that this talk is basic and I could Not Agree
> > More
> > I have taken the time to develop the framework for my next talk
> >  Structural Decomposition Of The Linux FileSystem #101
> > Please take this talk into consideration and I believe that this is very
> > high level discussion about the Linux Filesystem, and also tell me your
> > thoughts on it its pretty lengthy and incredibly detailed and requesting to
> > reply as soon as possible

https://www.linuxplumbersconf.org/event/4/abstracts/
 The best presentations are not about finished work, but rather problems,
 proposals, or proof-of-concept solutions that require face-to-face
 discussions and debate.

Thanks

  reply	other threads:[~2019-06-03  4:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30  6:09 Theodore Ts'o
2019-06-01  9:02 ` Leon Romanovsky
2019-06-01  9:43   ` Greg KH
     [not found]     ` <CAFTVhMc6cjQko4pMdK0Vq1wOj+Wv+sSgWzwULhVQQF9+AL02JA@mail.gmail.com>
2019-06-01 17:52       ` Tanish Shinde
2019-06-03  4:48         ` Leon Romanovsky [this message]
2019-06-17 13:33         ` Theodore Ts'o

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=20190603044809.GF5261@mtr-leonro.mtl.com \
    --to=leon@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=tanishshinde2006@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox