All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Petr Vorel <pvorel@suse.cz>
Cc: Richard Palethorpe <rpalethorpe@suse.com>,
	Xiao Yang <yangx.jy@cn.fujitsu.com>,
	ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] doc/maintainer: Add policy for new functionality
Date: Sat, 11 Dec 2021 11:56:03 -0500	[thread overview]
Message-ID: <YbTYI2iKkopqLIjx@vapier> (raw)
In-Reply-To: <YbTBgHwZQEigF/1v@pevik>


[-- Attachment #1.1: Type: text/plain, Size: 1177 bytes --]

On 11 Dec 2021 16:19, Petr Vorel wrote:
> > > Suggested-by: Cyril Hrubis <chrubis@suse.cz>
> > > Signed-off-by: Petr Vorel <pvorel@suse.cz>
> > > ---
> > >  doc/maintainer-patch-review-checklist.txt | 3 +++
> > >  1 file changed, 3 insertions(+)
> 
> > > diff --git a/doc/maintainer-patch-review-checklist.txt b/doc/maintainer-patch-review-checklist.txt
> > > index c7bb47810..4e2b267ac 100644
> > > --- a/doc/maintainer-patch-review-checklist.txt
> > > +++ b/doc/maintainer-patch-review-checklist.txt
> > > @@ -34,6 +34,9 @@ New test should
> > >    GPL-2.0-or-later; the licence for test (e.g. GPL-2.0) should not change
> > >    unless test is completely rewritten
> > >  * Old copyrights should be kept unless test is completely rewritten
> > > +* Tests for new functionality in mainline kernel should be merged after final
> > > +  release of kernel which contains that functionality (it's not enough when the
> > > +  feature gets into rc1, because it can be reverted in later rc if problematic).
> 
> > Sounds reasonable to me, but ideally this should be acked by the rest of
> > the maintainers.
> 
> Sure, this can wait :).

seems fine
-mike

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 60 bytes --]


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2021-12-13  8:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10 13:45 [LTP] [PATCH 1/1] doc/maintainer: Add policy for new functionality Petr Vorel
2021-12-10 16:12 ` Cyril Hrubis
2021-12-11 15:19   ` Petr Vorel
2021-12-11 16:56     ` Mike Frysinger [this message]
2021-12-12  3:23       ` Enji Cooper
2021-12-12  3:49 ` Li Wang
2021-12-13  7:32 ` Jan Stancek
2021-12-13  8:22 ` Richard Palethorpe
2021-12-13  9:05   ` Cyril Hrubis
2021-12-13  9:09     ` xuyang2018.jy
2021-12-13 11:17       ` Richard Palethorpe
2021-12-13 12:14         ` Cyril Hrubis
2021-12-13 14:17           ` Richard Palethorpe
2021-12-15 10:52             ` Petr Vorel
2021-12-15 11:32               ` Richard Palethorpe
2021-12-15 16:29                 ` Petr Vorel
2021-12-20  8:58                   ` Richard Palethorpe
2021-12-20 17:53                     ` Petr Vorel
2022-01-05 15:29                     ` Cyril Hrubis

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=YbTYI2iKkopqLIjx@vapier \
    --to=vapier@gentoo.org \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    --cc=rpalethorpe@suse.com \
    --cc=yangx.jy@cn.fujitsu.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.