From: Greg KH <greg@kroah.com>
To: Daniel Phillips <d.phillips@partner.samsung.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [topic] Richer internal block API
Date: Thu, 29 May 2014 16:43:11 -0700 [thread overview]
Message-ID: <20140529234311.GB12450@kroah.com> (raw)
In-Reply-To: <53877FBD.7060003@partner.samsung.com>
On Thu, May 29, 2014 at 11:43:09AM -0700, Daniel Phillips wrote:
> >> Not like btrfs is doing, the opposite really.
> > Good, post patches then :)
> >
> Is that a recommendation to develop a core API extension in a vacuum?
No, do it like any other core api changes, post patches that explain
what you want to do, and people will review them.
Come on, you know how this all works, we don't have to have meetings in
order to do design decisions that are "large".
greg k-h
next prev parent reply other threads:[~2014-05-29 23:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 17:49 Daniel Phillips
2014-05-29 18:13 ` Greg KH
2014-05-29 18:13 ` Daniel Phillips
2014-05-29 18:23 ` Greg KH
2014-05-29 18:43 ` Daniel Phillips
2014-05-29 23:43 ` Greg KH [this message]
2014-05-31 22:44 ` Daniel Phillips
2014-06-01 2:34 ` Greg KH
2014-06-02 17:33 ` Martin K. Petersen
2014-06-02 18:10 ` James Bottomley
2014-06-01 4:31 ` NeilBrown
2014-05-30 9:56 ` Lukáš Czerner
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=20140529234311.GB12450@kroah.com \
--to=greg@kroah.com \
--cc=d.phillips@partner.samsung.com \
--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