From: Jens Axboe <axboe@fb.com>
To: Kent Overstreet <kent.overstreet@gmail.com>,
<torvalds@linux-foundation.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] bcache revert
Date: Mon, 31 Aug 2015 13:14:07 -0600 [thread overview]
Message-ID: <55E4A77F.7030802@fb.com> (raw)
In-Reply-To: <20150831190050.GC27538@kmo-pixel>
On 08/31/2015 01:00 PM, Kent Overstreet wrote:
> Linus, please pull; this reverts a patch from Jens that was committed without
> CCing be or being mailed out to any of the lists. Said patch wasn't in any way a
> functional change and is something that damn well should have been discussed.
>
> Jens - what the goddamn fuck!? You've never touched the bcache code until now,
> and when you finally get interested this is what you do!?
>
> While I am sympathetic to the arguments in favor of your patch, there _are_ some
> damn good reasons I did it the way I did. If you want to have that discussion,
> feel free to mail your patch out again after the revert.
The patch was part of a larger series that I was working on, and I just
wanted to flush out that dependency. Christoph review and acked it, it
was by no means a sneaking in of a patch.
So calm down. Is there a bug? The previous code was crap, having hidden
returns in macros is horrible. The upstream bcache code has been
effectively unmaintained for more than a year, and THIS patch is now a
problem? Get real.
--
Jens Axboe
next prev parent reply other threads:[~2015-08-31 19:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 19:00 [GIT PULL] bcache revert Kent Overstreet
2015-08-31 19:14 ` Jens Axboe [this message]
2015-08-31 19:29 ` Kent Overstreet
2015-08-31 19:42 ` Jens Axboe
2015-08-31 19:53 ` Kent Overstreet
2015-08-31 20:06 ` Jens Axboe
2015-08-31 20:17 ` Kent Overstreet
2015-08-31 20:25 ` Jens Axboe
2015-08-31 20:42 ` Kent Overstreet
2015-08-31 20:47 ` Jens Axboe
2015-08-31 20:57 ` 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=55E4A77F.7030802@fb.com \
--to=axboe@fb.com \
--cc=kent.overstreet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.