From: Artem Bityutskiy <dedekind1@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Artem Bityutskiy <dedekind1@gmail.com>, linux-kernel@vger.kernel.org
Subject: [GIT PULL] UBIFS fixes for 3.1
Date: Tue, 06 Sep 2011 06:22:36 +0300 [thread overview]
Message-ID: <20110906032236.19050.6306.sendpatchset@localhost.localdomain> (raw)
Hi Linus,
please pull a fix an UBIFS regression - we mistakingly linked debuggin messages
even when debugging was disabled.
The following changes since commit 93ee7a9340d64f20295aacc3fb6a22b759323280:
Linux 3.1-rc2 (2011-08-14 15:09:08 -0700)
are available in the git repository at:
git://git.infradead.org/ubifs-2.6.git linux-next
Michal Marek (1):
UBIFS: not build debug messages with CONFIG_UBIFS_FS_DEBUG disabled
fs/ubifs/debug.h | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
Thanks,
Artem.
next reply other threads:[~2011-09-06 3:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 3:22 Artem Bityutskiy [this message]
2011-09-09 6:47 ` [GIT PULL] UBIFS fixes for 3.1 Artem Bityutskiy
2011-09-09 14:41 ` Linus Torvalds
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=20110906032236.19050.6306.sendpatchset@localhost.localdomain \
--to=dedekind1@gmail.com \
--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).