public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Jan Kara <jack@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] udf: Compilation fixes
Date: Wed, 30 Jan 2008 15:00:09 -0800	[thread overview]
Message-ID: <20080130150009.f1d2d162.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080130150737.GE16140@duck.suse.cz>

On Wed, 30 Jan 2008 16:07:37 +0100
Jan Kara <jack@suse.cz> wrote:

>   Hi,
> 
>   the patch below makes UDF compile in -mm kernel (against 2.6.24-rc8-mm1).
> Please apply.
> 
> 									Honza
> -- 
> Jan Kara <jack@suse.cz>
> SUSE Labs, CR
> ---
> 
> Make UDF compile - fixes fallout from previous cleanup patches.
> 
> Signed-off-by: Jan Kara <jack@suse.cz>
> 
> diff -rupX /home/jack/.kerndiffexclude linux-2.6.24-rc8-mm1-1-udf_fpos_fix/fs/udf/ialloc.c linux-2.6.24-rc8-mm1-2-udf_add_entry_fix/fs/udf/ialloc.c

Please prefer to put not-for-the-changelog text after the "^---" rather
than prior to the changelog.

When fixing compile errors and warnings, please always quote the compiler
output so we can see what is being fixed.

This patch doesn't apply to my tree and UDF presently compiles OK.  And it
compiled OK in 2.6.24-rc8-mm1 so I am at a loss to know what's going on
here.

Please check http://userweb.kernel.org/~akpm/mmotm/ with your mysteryconfig
and see if we still need any fixes.   Beware that this mmotm snapshot is full
of git conflicts which I haven't bothered fixing (because they're different each
time I pull the trees).  But UDF compiles OK.



      reply	other threads:[~2008-01-30 23:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30 15:07 [PATCH] udf: Compilation fixes Jan Kara
2008-01-30 23:00 ` Andrew Morton [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=20080130150009.f1d2d162.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.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