From: Kevin Wolf <kwolf@redhat.com>
To: Keith Busch <kbusch@kernel.org>
Cc: Klaus Jensen <its@irrelevant.dk>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [PATCH] MAINTAINERS: update nvme entry
Date: Wed, 8 Jul 2020 19:13:37 +0200 [thread overview]
Message-ID: <20200708171337.GG4902@linux.fritz.box> (raw)
In-Reply-To: <20200708170330.GA2288218@dhcp-10-100-145-180.wdl.wdc.com>
Am 08.07.2020 um 19:03 hat Keith Busch geschrieben:
> On Tue, Jul 07, 2020 at 05:26:13PM +0200, Kevin Wolf wrote:
> > Am 06.07.2020 um 21:43 hat Keith Busch geschrieben:
> > > The nvme emulated device development pace has increased recently. Klaus
> > > has offered to co-maintain, and since we have many new contributions
> > > coming through, we're adding a repository to accumulate and test new
> > > features.
> > >
> > > Cc: Klaus Jensen <its@irrelevant.dk>
> > > Signed-off-by: Keith Busch <kbusch@kernel.org>
> >
> > I assume that you'll merge this as the first thing through your new
> > tree, so instead of applying, I'll just add:
>
> Thanks, I've started the new branch with this as the first commit. We'll
> wait at least a few more days to see if we've agreement on new patches
> before sending our pull request.
We're now in the freeze for 5.1 anyway, so everything except fixes (and
I guess the MAINTAINERS update if you do send something) will have to
wait until after the release.
Kevin
prev parent reply other threads:[~2020-07-08 22:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 19:43 [PATCH] MAINTAINERS: update nvme entry Keith Busch
2020-07-07 6:16 ` Klaus Jensen
2020-07-07 6:30 ` Philippe Mathieu-Daudé
2020-07-07 6:49 ` Klaus Jensen
2020-07-07 15:26 ` Kevin Wolf
2020-07-08 17:03 ` Keith Busch
2020-07-08 17:13 ` Kevin Wolf [this message]
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=20200708171337.GG4902@linux.fritz.box \
--to=kwolf@redhat.com \
--cc=its@irrelevant.dk \
--cc=kbusch@kernel.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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.