All of lore.kernel.org
 help / color / mirror / Atom feed
From: xfs@oss.sgi.com
To: xfs@oss.sgi.com
Subject: [XFS updates] XFS development tree branch, for-next, updated. for-linus-v3.11-rc1-2-12162-g2c2bcc0
Date: Tue, 13 Aug 2013 14:20:00 -0500 (CDT)	[thread overview]
Message-ID: <20130813192000.CE3A87F80@oss.sgi.com> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "XFS development tree".

The branch, for-next has been updated
  2c2bcc0 xfs: call roundup_64() to calculate the min_logblks
      from  3e7b91cf8c19d89e55df5f05e3010446dbdaba77 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 2c2bcc0735f4ab052559b539f3fcab4087187232
Author: Jie Liu <jeff.liu@oracle.com>
Date:   Tue Aug 13 13:32:00 2013 +0800

    xfs: call roundup_64() to calculate the min_logblks
    
    Replace roundup() with roundup_64() as we calculate min_logblks
    with 64-bit divisions.  Hence, call roundup() will cause the
    following error while compiling a 32-bit kernel:
    
    fs/built-in.o: In function `xfs_log_calc_minimum_size':
    fs/xfs/xfs_log_rlimit.c:140: undefined reference to `__udivdi3'
    
    Reported-by: Fengguang Wu <fengguang.wu@intel.com>
    Cc: Dave Chinner <dchinner@redhat.com>
    Signed-off-by: Jie Liu <jeff.liu@oracle.com>
    Reviewed-by: Dave Chinner <dchinner@redhat.com>
    Signed-off-by: Ben Myers <bpm@sgi.com>

-----------------------------------------------------------------------

Summary of changes:
 fs/xfs/xfs_log_rlimit.c | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)


hooks/post-receive
-- 
XFS development tree

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

                 reply	other threads:[~2013-08-13 19:20 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=20130813192000.CE3A87F80@oss.sgi.com \
    --to=xfs@oss.sgi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.