The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Bob Copeland <me@bobcopeland.com>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: linux-karma-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] omfs: fix warning
Date: Sat, 2 Aug 2008 09:24:10 -0400	[thread overview]
Message-ID: <20080802132410.GA18961@hash.localnet> (raw)
In-Reply-To: <20080802080725.GA4856@orion>

On Sat, Aug 02, 2008 at 12:07:25PM +0400, Alexander Beregalov wrote:
> From: Alexander Beregalov <a.beregalov@gmail.com>
> 
> omfs: fix warnings
> 
> fs/omfs/inode.c:495: warning: format '%llx' expects type 'long long
> 	unsigned int', but argument 2 has type 'u64'
> fs/omfs/inode.c:495: warning: format '%llx' expects type 'long
> 	long unsigned int', but argument 3 has type '__be64'
> 
> Signed-off-by: Alexander Beregalov <a.beregalov@gmail.com>
> Cc: Bob Copeland <me@bobcopeland.com>

Thanks!

Acked-by: Bob Copeland <me@bobcopeland.com>

(And I'm downloading cross compilers as I type this.)

Andrew, should I continue to send omfs patches through you, or do I need
to publish a git repo?

>  			"super and root blocks (%llx, %llx)\n",
> -			sbi->s_num_blocks, be64_to_cpu(omfs_rb->r_num_blocks));
> +			(unsigned long long)sbi->s_num_blocks,
> +			(unsigned long long)be64_to_cpu(omfs_rb->r_num_blocks));
>  		goto out_brelse_bh2;

-- 
Bob Copeland %% www.bobcopeland.com


      reply	other threads:[~2008-08-02 13:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-02  8:07 [PATCH] omfs: fix warning Alexander Beregalov
2008-08-02 13:24 ` Bob Copeland [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=20080802132410.GA18961@hash.localnet \
    --to=me@bobcopeland.com \
    --cc=a.beregalov@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-karma-devel@lists.sourceforge.net \
    --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