From: Cyril Hrubis <chrubis@suse.cz>
To: Jan Kara <jack@suse.cz>
Cc: ltp-list@lists.sourceforge.net, Amir Goldstein <amir73il@gmail.com>
Subject: Re: [LTP] [PATCH] inotify07: Add test for kernel crash during event notification
Date: Thu, 10 May 2018 13:06:40 +0200 [thread overview]
Message-ID: <20180510110640.GB8934@rei> (raw)
In-Reply-To: <20180509130356.czmvg4b3ndrtosir@quack2.suse.cz>
Hi!
> > > BTW, Cyril, do you have a preference between github pull request
> > > and posting the patch to the list?
> > > I suppose I should have posted to fsdevel and CC Jan anyway...
> >
> > I do prefer mailing list over pull requests but I work with both.
>
> Cyril, should I rebase on top of that pull request or will you handle the
> conflict on your own?
I usually handle simple enough collisions myself, no need to rebase and
resend just because of that.
Also as we are in the middle of pre-release freeze please be patient as
the review will have to wait at least a week or two.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2018-05-10 11:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 11:42 [LTP] [PATCH] inotify07: Add test for kernel crash during event notification Jan Kara
2018-05-03 15:06 ` Cyril Hrubis
[not found] ` <CAOQ4uxgQK9HtojVteoQNJfaP5qVX67HxmHoQ-XKLtjaTq4==Lg@mail.gmail.com>
2018-05-04 14:06 ` Cyril Hrubis
[not found] ` <20180509130356.czmvg4b3ndrtosir@quack2.suse.cz>
2018-05-10 11:06 ` Cyril Hrubis [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-03 15:22 Jan Kara
2018-05-23 11:08 ` Cyril Hrubis
2018-05-23 11:20 ` 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=20180510110640.GB8934@rei \
--to=chrubis@suse.cz \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
/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.