From: Kent Overstreet <kmo-PEzghdH756F8UrSeD/g0lQ@public.gmane.org>
To: Jens Axboe <axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
Cc: torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] Fix for bcache regression
Date: Thu, 10 Oct 2013 19:38:11 -0700 [thread overview]
Message-ID: <20131011023811.GA19050@kmo> (raw)
In-Reply-To: <20131011022313.GA31029-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
On Thu, Oct 10, 2013 at 08:23:13PM -0600, Jens Axboe wrote:
> On Thu, Oct 10 2013, Kent Overstreet wrote:
> > Linus, please apply - the last fix in the bugfix series I sent you had an
> > embarassing screwup...
> >
> > For 3.13, shall I start sending you pull requests directly?
>
> Sorry I dropped the ball on that one, it's the first time ever I've
> missed a deadline. It's being ramped up again, kernel time will be
> plenty again shortly.
No worries, I've been behind on plenty of stuff too and wouldn't have
much room to complain :)
Probably best that the giant pull ended up waiting a bit longer anyways
with the bugs I've still been fixing. Anyways, bcache is self contained
enough I doubt it really matters, so whatever the two of you prefer is
fine by me.
WARNING: multiple messages have this Message-ID (diff)
From: Kent Overstreet <kmo@daterainc.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-bcache@vger.kernel.org
Subject: Re: [PATCH] Fix for bcache regression
Date: Thu, 10 Oct 2013 19:38:11 -0700 [thread overview]
Message-ID: <20131011023811.GA19050@kmo> (raw)
In-Reply-To: <20131011022313.GA31029@kernel.dk>
On Thu, Oct 10, 2013 at 08:23:13PM -0600, Jens Axboe wrote:
> On Thu, Oct 10 2013, Kent Overstreet wrote:
> > Linus, please apply - the last fix in the bugfix series I sent you had an
> > embarassing screwup...
> >
> > For 3.13, shall I start sending you pull requests directly?
>
> Sorry I dropped the ball on that one, it's the first time ever I've
> missed a deadline. It's being ramped up again, kernel time will be
> plenty again shortly.
No worries, I've been behind on plenty of stuff too and wouldn't have
much room to complain :)
Probably best that the giant pull ended up waiting a bit longer anyways
with the bugs I've still been fixing. Anyways, bcache is self contained
enough I doubt it really matters, so whatever the two of you prefer is
fine by me.
next prev parent reply other threads:[~2013-10-11 2:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 0:31 [PATCH] Fix for bcache regression Kent Overstreet
2013-10-11 0:31 ` [PATCH] bcache: Fix a null ptr deref regression Kent Overstreet
[not found] ` <1381451475-24551-1-git-send-email-kmo-PEzghdH756F8UrSeD/g0lQ@public.gmane.org>
2013-10-11 2:23 ` [PATCH] Fix for bcache regression Jens Axboe
2013-10-11 2:23 ` Jens Axboe
[not found] ` <20131011022313.GA31029-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
2013-10-11 2:38 ` Kent Overstreet [this message]
2013-10-11 2:38 ` 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=20131011023811.GA19050@kmo \
--to=kmo-pezghdh756f8ursed/g0lq@public.gmane.org \
--cc=axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.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.