public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Anca Emanuel <anca.emanuel@gmail.com>
Cc: Dave Jones <davej@redhat.com>,
	"Bityutskiy, Artem" <artem.bityutskiy@intel.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PULL REQUEST] More UBI/UBIFS changes for 3.3
Date: Sun, 15 Jan 2012 21:22:33 +0200	[thread overview]
Message-ID: <1326655399.2201.2.camel@koala> (raw)
In-Reply-To: <CAJL_dMsugowERsv8qHuaWZB3yEstqrB3d+So-ive-EGRoi4OMg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 615 bytes --]

On Sun, 2012-01-15 at 11:19 +0200, Anca Emanuel wrote:
> On Sat, Jan 14, 2012 at 8:48 PM, Dave Jones <davej@redhat.com> wrote:
> 
> > This introduced a compile failure if CONFIG_UBIFS_FS_DEBUG is unset.
> >
> > fs/ubifs/journal.c: In function ‘ubifs_jnl_write_data’:
> > fs/ubifs/journal.c:700:2: error: implicit declaration of function ‘dbg_jnlk’ [-Werror=implicit-function-declaration]
> 
> And now it is in Linus tree.

Sorry for this, I've sent today another pull request with a fix. I was
not careful enough to test UBIFS when debugging is disabled.

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

      reply	other threads:[~2012-01-15 19:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-13 12:11 [PULL REQUEST] More UBI/UBIFS changes for 3.3 Bityutskiy, Artem
2012-01-14 18:48 ` Dave Jones
2012-01-15  9:19   ` Anca Emanuel
2012-01-15 19:22     ` Artem Bityutskiy [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=1326655399.2201.2.camel@koala \
    --to=dedekind1@gmail.com \
    --cc=anca.emanuel@gmail.com \
    --cc=artem.bityutskiy@intel.com \
    --cc=davej@redhat.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