From: Christoph Hellwig <hch@infradead.org>
To: torvalds@linux-foundation.org
Cc: jlbec@evilplan.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] a configfs fix for -rc2
Date: Sat, 2 Apr 2016 18:00:05 +0200 [thread overview]
Message-ID: <20160402160005.GA29514@infradead.org> (raw)
Hi Linus,
The following changes since commit 1ae1602de028acaa42a0f6ff18d19756f8e825c6:
configfs: switch ->default groups to a linked list (2016-03-06 16:11:24 +0100)
are available in the git repository at:
git://git.infradead.org/users/hch/configfs.git tags/configfs-for-linus-2
for you to fetch changes up to 96c22a3293512ba684e73a981196430f524689da:
configfs: fix CONFIGFS_BIN_ATTR_[RW]O definitions (2016-03-25 19:10:03 +0100)
----------------------------------------------------------------
Configfs fix for 4.6-rc2:
- a trivial fix to the recently introduced binary attribute helper
macros
----------------------------------------------------------------
Octavian Purdila (1):
configfs: fix CONFIGFS_BIN_ATTR_[RW]O definitions
include/linux/configfs.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
reply other threads:[~2016-04-02 16:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160402160005.GA29514@infradead.org \
--to=hch@infradead.org \
--cc=jlbec@evilplan.org \
--cc=linux-fsdevel@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).