All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Kent Overstreet <koverstreet@google.com>
Cc: chetan loke <loke.chetan@gmail.com>,
	nauman@google.com, dm-devel@redhat.com,
	lsf-pc@lists.linux-foundation.org, linux-scsi@vger.kernel.org,
	Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [Lsf-pc] [Topic] Bcache
Date: Wed, 14 Mar 2012 14:47:53 -0400	[thread overview]
Message-ID: <20120314184753.GA9358@infradead.org> (raw)
In-Reply-To: <CAH+dOx+M5so=YOx=O2vUjpdHsG+oiGsJh3GouoVq+twL+tO3Yw@mail.gmail.com>

On Wed, Mar 14, 2012 at 02:41:35PM -0400, Kent Overstreet wrote:
> If you want me to implement bcache differently, shouldn't you explain
> why? I'm not sure why I _have_ to justify my decisions to you.

You don't have to - unless you want to get bcache merged into the
mainline kernel.  If you don't want to you probably shouldn't bother
appearing at the LSF, though.


  reply	other threads:[~2012-03-14 18:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 13:32 [Topic] Bcache Kent Overstreet
2012-03-14 15:53 ` [Lsf-pc] " Vivek Goyal
2012-03-14 17:24   ` Kent Overstreet
2012-03-14 22:01     ` Bcache Mike Snitzer
2012-03-14 22:09       ` [Lsf-pc] Bcache Williams, Dan J
2012-03-15 17:27       ` Bcache Kent Overstreet
2012-03-15 20:17         ` Bcache Mike Snitzer
2012-03-15 22:59           ` Bcache Kent Overstreet
2012-03-16  1:45             ` Bcache Mike Snitzer
2012-03-15 19:43     ` [Lsf-pc] [Topic] Bcache Vivek Goyal
2012-03-15 23:46       ` Kent Overstreet
2012-03-14 18:12   ` chetan loke
2012-03-14 18:17     ` Kent Overstreet
2012-03-14 18:33       ` chetan loke
2012-03-14 18:41         ` Kent Overstreet
2012-03-14 18:47           ` Christoph Hellwig [this message]
2012-03-14 19:04           ` chetan loke
2012-03-15 17:01             ` Kent Overstreet
2012-03-14 18:54         ` Ted Ts'o
2012-03-14 19:22           ` chetan loke
2012-03-15 17:02           ` Kent Overstreet

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=20120314184753.GA9358@infradead.org \
    --to=hch@infradead.org \
    --cc=dm-devel@redhat.com \
    --cc=koverstreet@google.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=loke.chetan@gmail.com \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=nauman@google.com \
    --cc=vgoyal@redhat.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 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.