public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Stefan Schmidt <stefan@datenfreihafen.org>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Jan Kara <jack@suse.cz>,
	linux-ext4@vger.kernel.org
Subject: Re: [PATCH] fs/jbd: Export log_start_commit to fix ext3 build
Date: Thu, 12 Nov 2009 10:34:03 +0100	[thread overview]
Message-ID: <20091112093403.GA14528@duck.suse.cz> (raw)
In-Reply-To: <20091112085843.GA2682@excalibur.local>

On Thu 12-11-09 09:58:43, Stefan Schmidt wrote:
> From 9bf22057947bfaeef14287dd03ac8f058e4dd43a Mon Sep 17 00:00:00 2001
> From: Stefan Schmidt <stefan@datenfreihafen.org>
> Date: Thu, 12 Nov 2009 09:53:50 +0100
> Subject: [PATCH] fs/jbd: Export log_start_commit to fix ext3 build.
> 
> This fixes:
> ERROR: "log_start_commit" [fs/ext3/ext3.ko] undefined!
> 
> Signed-off-by: Stefan Schmidt <stefan@datenfreihafen.org>
  Argh :(. Thanks! My test kernels have ext3 compiled in... Merged and will
send Linus pull request in a minute.

									Honza

> ---
>  fs/jbd/journal.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/fs/jbd/journal.c b/fs/jbd/journal.c
> index 49d5cd6..4160afa 100644
> --- a/fs/jbd/journal.c
> +++ b/fs/jbd/journal.c
> @@ -73,6 +73,7 @@ EXPORT_SYMBOL(journal_errno);
>  EXPORT_SYMBOL(journal_ack_err);
>  EXPORT_SYMBOL(journal_clear_err);
>  EXPORT_SYMBOL(log_wait_commit);
> +EXPORT_SYMBOL(log_start_commit);
>  EXPORT_SYMBOL(journal_start_commit);
>  EXPORT_SYMBOL(journal_force_commit_nested);
>  EXPORT_SYMBOL(journal_wipe);
> -- 
> 1.6.5.2
> 
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

      reply	other threads:[~2009-11-12  9:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12  8:58 [PATCH] fs/jbd: Export log_start_commit to fix ext3 build Stefan Schmidt
2009-11-12  9:34 ` Jan Kara [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=20091112093403.GA14528@duck.suse.cz \
    --to=jack@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefan@datenfreihafen.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