All of lore.kernel.org
 help / color / mirror / Atom feed
From: chrubis@suse.cz
To: Zorro Lang <zlang@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] fs/fsstress: modify compile warning about fsstress.c
Date: Wed, 3 Sep 2014 10:17:48 +0200	[thread overview]
Message-ID: <20140903081748.GA18674@rei.suse.cz> (raw)
In-Reply-To: <5406CE2C.5080006@redhat.com>

Hi!
> >> when compile kernel/fs/fsstress/fsstress.c, some warning always be printed.
> >> Because there is a new field 'isxfs' be added in opdesc_t struct,
> >> but some lines of opdesc_t ops[] forget to init this field.
> > Pushed, thanks.
> >
> Thank you very much.
> 
> How about the other patch, named "fs/fsstress: prevent orphan and zombie 
> processes to be left".
> That is we really want to be merged.

I will have a look ASAP.

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  parent reply	other threads:[~2014-09-03  8:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1409672694-32108-1-git-send-email-zlang@redhat.com>
2014-09-03  7:22 ` [LTP] [PATCH] fs/fsstress: modify compile warning about fsstress.c chrubis
     [not found]   ` <5406CE2C.5080006@redhat.com>
2014-09-03  8:17     ` chrubis [this message]
2014-08-29  7:05 Zorro Lang
  -- strict thread matches above, loose matches on Subject: below --
2014-08-20  2:37 Zorro Lang
2014-09-02 13:21 ` chrubis
     [not found]   ` <5405E5EC.4010406@redhat.com>
2014-09-02 16:00     ` chrubis
2014-08-12 10:00 Zorro Lang

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=20140903081748.GA18674@rei.suse.cz \
    --to=chrubis@suse.cz \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=zlang@redhat.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.