linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@fusionio.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	<linux-btrfs@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	"JBottomley@parallels.com" <JBottomley@parallels.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [GIT PULL] Btrfs fixup
Date: Sun, 3 Mar 2013 07:32:49 -0500	[thread overview]
Message-ID: <20130303123249.GB18135@shiny.masoncoding.com> (raw)

Hi Linus,

Geert and James both sent this one in, sorry guys.

git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus

Geert Uytterhoeven (1) commits (+1/-0):
    btrfs/raid56: Add missing #include <linux/vmalloc.h>

Total: (1) commits (+1/-0)

 fs/btrfs/raid56.c | 1 +
 1 file changed, 1 insertion(+)

             reply	other threads:[~2013-03-03 12:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-03 12:32 Chris Mason [this message]
2013-03-04 18:30 ` [GIT PULL] Btrfs fixup Zach Brown

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=20130303123249.GB18135@shiny.masoncoding.com \
    --to=chris.mason@fusionio.com \
    --cc=JBottomley@parallels.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-btrfs@vger.kernel.org \
    --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 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).