From: Tanish Shinde <tanishshinde2006@gmail.com>
To: 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: Sat, 1 Jun 2019 23:22:32 +0530 [thread overview]
Message-ID: <CAFTVhMen6LqB2p8Ptq0CeUWw9hiJDVU6Z_70yMbQLSG2HbJVOQ@mail.gmail.com> (raw)
In-Reply-To: <CAFTVhMc6cjQko4pMdK0Vq1wOj+Wv+sSgWzwULhVQQF9+AL02JA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2326 bytes --]
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
>
> Thanking You
> Tanish Vishal Shinde
>
> On Sat, 1 Jun 2019 at 21:50, Greg KH <gregkh@linuxfoundation.org> wrote:
>
>> On Sat, Jun 01, 2019 at 12:02:24PM +0300, Leon Romanovsky wrote:
>> > On Thu, May 30, 2019 at 02:09:39AM -0400, Theodore Ts'o wrote:
>> > > From: Tanish Shinde <tanish.shinde2006@gmail.com>
>> > >
>> > > [ Note: The following abstract was submitted via the Linux Plumbers
>> > > Conference website. Per the instructions that were posted for the
>> > > Maintainer's / Kernel Summit Call for Proposals[1], the proposal
>> > > should also be posted on the ksummit-discuss list, so that people
>> > > can comment on the proposal, and perhaps start a discussion before
>> > > the summit.
>> > >
>> > > [1] https://lwn.net/Articles/788378/
>> > >
>> > > Please note that topic proposals for both the Kernel Summit and the
>> > > Maintainer's Summit are still welcome, and the deadline has been
>> > > extended to June 3rd. -- Ted ]
>> > >
>> > > The Linux kernel is the core of a large and complex operating system,
>> and while it's huge, it is well organized in terms of subsystems and
>> layers. In this talk, the viewer explores the general structure of the
>> Linux kernel and gets to know its major subsystems and core interfaces.
>> > >
>> > > In This Talk We Will Discuss The Following Topics
>> > >
>> > > * The Fundamental Architecture Of Linux
>> > > * System Call Interface & Process Management
>> > > * Memory Management & The Virtual File System
>> > > * Network Stack & Device Drivers
>> > > * Architecture Dependent Code
>> >
>> > IMHO, it is far too beginner topic for LPC and definitely for KS too.
>>
>> I agree, this really is too much of a beginner-oriented talk for this
>> conference.
>>
>> thanks,
>>
>> greg k-h
>>
>
[-- Attachment #2: Type: text/html, Size: 3618 bytes --]
next prev parent reply other threads:[~2019-06-01 17:52 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 [this message]
2019-06-03 4:48 ` Leon Romanovsky
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=CAFTVhMen6LqB2p8Ptq0CeUWw9hiJDVU6Z_70yMbQLSG2HbJVOQ@mail.gmail.com \
--to=tanishshinde2006@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox