From: Eugeniu Rosca <erosca@de.adit-jv.com>
To: shuah <shuah@kernel.org>
Cc: Eugeniu Rosca <erosca@de.adit-jv.com>,
"George G. Davis" <george_davis@mentor.com>,
Eugeniu Rosca <roscaeugeniu@gmail.com>,
Jerry Hoemann <jerry.hoemann@hpe.com>,
Colin Ian King <colin.king@canonical.com>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] selftests: watchdog: Validate optional file argument
Date: Tue, 17 Sep 2019 19:50:56 +0200 [thread overview]
Message-ID: <20190917175056.GA24224@vmlxhi-102.adit-jv.com> (raw)
In-Reply-To: <374127ff-d06f-fcc3-d317-5614dfdc5a71@kernel.org>
On Tue, Sep 17, 2019 at 11:44:45AM -0600, shuah wrote:
> On 9/17/19 10:54 AM, Eugeniu Rosca wrote:
> > Shuah,
> >
> > On Tue, Sep 17, 2019 at 09:25:31AM -0600, shuah wrote:
> >
> > [..]
> >
> > > I want two patches and the first one with
> > > Fixes tag.
> >
>
> These two patches need to be separate. The first one is a fix and
> the second is an enhancement.
That was exactly the idea of v1.
>
> Please send two patches - the first one with Fixes tag.
Can you please pick [v1] series from below:
- https://patchwork.kernel.org/patch/11136283/
- https://patchwork.kernel.org/patch/11136285/
with adding a one-liner Fixes tag to the first patch?
--
Best Regards,
Eugeniu.
next prev parent reply other threads:[~2019-09-17 17:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 18:49 [PATCH v2] selftests: watchdog: Validate optional file argument George G. Davis
2019-09-17 1:19 ` shuah
2019-09-17 14:54 ` Eugeniu Rosca
2019-09-17 15:25 ` shuah
2019-09-17 16:54 ` Eugeniu Rosca
2019-09-17 17:44 ` shuah
2019-09-17 17:50 ` Eugeniu Rosca [this message]
2019-09-17 18:05 ` shuah
2019-09-17 18:32 ` George G. Davis
2019-09-17 18:43 ` George G. Davis
2019-09-17 18:51 ` Eugeniu Rosca
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=20190917175056.GA24224@vmlxhi-102.adit-jv.com \
--to=erosca@de.adit-jv.com \
--cc=colin.king@canonical.com \
--cc=george_davis@mentor.com \
--cc=jerry.hoemann@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=roscaeugeniu@gmail.com \
--cc=shuah@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;
as well as URLs for NNTP newsgroup(s).