From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "sfr@canb.auug.org.au" <sfr@canb.auug.org.au>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
"hch@infradead.org" <hch@infradead.org>,
"jack@suse.cz" <jack@suse.cz>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
"tytso@mit.edu" <tytso@mit.edu>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: dax-misc branch for linux-next
Date: Tue, 17 May 2016 18:36:47 +0000 [thread overview]
Message-ID: <1463510194.29294.77.camel@intel.com> (raw)
Hi Stephen,
I understand this is a bit out of the norm, but:
Could you please merge
https://git.kernel.org/cgit/linux/kernel/git/nvdimm/nvdimm.git dax-misc
into linux-next for some coverage.
It is a bit late to the ready-before-merge-window deadline, due to
having to coordinate dependencies between trees/patchsets. I'm hoping to
send a pull request for this later in the merge window (once ext4 is
merged).
Thanks,
-Vishal
next reply other threads:[~2016-05-17 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 18:36 Verma, Vishal L [this message]
2016-05-18 3:34 ` dax-misc branch for linux-next Stephen Rothwell
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=1463510194.29294.77.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=dan.j.williams@intel.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=sfr@canb.auug.org.au \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).