linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Manish Katiyar <mkatiyar@gmail.com>
Cc: Jan Kara <jack@suse.cz>, ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] : Remove incompatible pointer assignment warning in ext4 quota operations
Date: Thu, 12 Feb 2009 06:47:36 -0500	[thread overview]
Message-ID: <20090212114736.GA13040@mini-me.lan> (raw)
In-Reply-To: <ea11fea30902120054g5192f269y5cdf34795d9f8e1e@mail.gmail.com>

On Thu, Feb 12, 2009 at 02:24:17PM +0530, Manish Katiyar wrote:
> On Mon, Feb 2, 2009 at 9:40 PM, Jan Kara <jack@suse.cz> wrote:
> >> On Wed, Jan 28, 2009 at 10:47 AM, Manish Katiyar <mkatiyar@gmail.com> wrote:
> >> > Below patch removes the following warning during compilation :
> >> >
> >> >  CC [M]  fs/ext4/super.o
> >> > fs/ext4/super.c:949: warning: initialization from incompatible pointer type
> >> >  LD [M]  fs/ext4/ext4.o
> >>
> >> Sorry,
> >>
> >> Tha correct patch is here.
> >>
> >> Signed-off-by: Manish Katiyar <mkatiyar@gmail.com>
> >  Looks fine to me.
> > Acked-by: Jan Kara <jack@suse.cz>
> 
> Hi Jan,
> 
> A simple doubt. Patches acked by you will be automatically picked up
> or will I have to resend it with your ack added ??

Actually, in this case Jan should pick up the patch and merge it with
Mingming's ext4 quota patch which is being carried in his tree.  The
current ext4 code doesn't have ext4_get_reserved_space() at all.

							- Ted

  reply	other threads:[~2009-02-12 16:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28  5:17 [PATCH] : Remove incompatible pointer assignment warning in ext4 quota operations Manish Katiyar
2009-01-28  5:21 ` Manish Katiyar
2009-01-30 15:00   ` Manish Katiyar
2009-02-02 16:10   ` Jan Kara
2009-02-12  8:54     ` Manish Katiyar
2009-02-12 11:47       ` Theodore Tso [this message]
2009-02-12 14:22       ` Jan Kara

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=20090212114736.GA13040@mini-me.lan \
    --to=tytso@mit.edu \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=mkatiyar@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).