From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Dmitry Antipov <dmantipov@yandex.ru>,
Jonathan Corbet <corbet@lwn.net>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] doc: development-process: add notice on testing
Date: Fri, 23 Jan 2026 12:50:26 +0200 [thread overview]
Message-ID: <aXNScixKm5L2tQIv@smile.fi.intel.com> (raw)
In-Reply-To: <d9147abf-0b08-40e2-aa49-821c953f5fc7@infradead.org>
On Thu, Jan 22, 2026 at 11:19:48PM -0800, Randy Dunlap wrote:
> On 1/22/26 11:15 PM, Dmitry Antipov wrote:
> > Add testing notice to "Before creating patches" section.
> >
> > Suggested-by: Andy Shevchenko <andriy.shevchenko@intel.com>
> > Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru>
>
> Acked-by: Randy Dunlap <rdunlap@infradead.org>
>
> Andy also Acked it. I think you could/should include
s/could// --> should
> his Ack here as well.
Yes. Carrying on the given tags is the author's responsibility.
Otherwise, you should explain clearly why the given tag is not
taking into account.
For this time I do it myself again, but next time don't forget doing that,
please.
Acked-by: Andy Shevchenko <andriy.shevchenko@intel.com>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-01-23 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 11:15 [PATCH] " Dmitry Antipov
2026-01-22 11:56 ` Andy Shevchenko
2026-01-22 18:28 ` Randy Dunlap
2026-01-23 7:15 ` [PATCH v2] " Dmitry Antipov
2026-01-23 7:19 ` Randy Dunlap
2026-01-23 10:50 ` Andy Shevchenko [this message]
2026-02-02 17:02 ` Jonathan Corbet
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=aXNScixKm5L2tQIv@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=corbet@lwn.net \
--cc=dmantipov@yandex.ru \
--cc=linux-doc@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=workflows@vger.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