From: Oliver Sang <oliver.sang@intel.com>
To: "Liam R. Howlett" <Liam.Howlett@oracle.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>, <oliver.sang@intel.com>
Subject: Re: [PATCH 2/3] maple_tree: use preallocations in mas_store_gfp()
Date: Fri, 3 Nov 2023 10:37:18 +0800 [thread overview]
Message-ID: <ZURc3u2BdMWulbpr@xsang-OptiPlex-9020> (raw)
In-Reply-To: <20231101165914.3bqsjmfbqwktlalz@revolver>
hi, Liam,
On Wed, Nov 01, 2023 at 12:59:14PM -0400, Liam R. Howlett wrote:
> * Oliver Sang <oliver.sang@intel.com> [231027 01:59]:
> > hi, Liam,
...
> > want to consult if it's ok to send to the mailing list but not cc any
> > individual mail in case we find regression for future version?
>
> No, no change needed. I can NACK in the future.
>
> Would it stop if I replied:
>
> NACK - Stopping the bot from testing this further.
got it. Thanks!
>
> Thanks,
> Liam
next prev parent reply other threads:[~2023-11-03 2:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 20:16 [PATCH 0/3] align maple tree write paths Sidhartha Kumar
2023-10-09 20:16 ` [PATCH 1/3] maple_tree: introduce mas_prealloc_calc() Sidhartha Kumar
2023-10-09 22:25 ` kernel test robot
2023-10-10 22:13 ` Sidhartha Kumar
2023-10-10 11:06 ` kernel test robot
2023-10-18 2:53 ` kernel test robot
2023-10-09 20:16 ` [PATCH 2/3] maple_tree: use preallocations in mas_store_gfp() Sidhartha Kumar
2023-10-10 3:03 ` Peng Zhang
2023-10-11 0:17 ` Sidhartha Kumar
2023-10-11 7:40 ` Peng Zhang
2023-10-10 18:15 ` Liam R. Howlett
2023-10-25 9:52 ` kernel test robot
2023-10-26 17:16 ` Liam R. Howlett
2023-10-27 5:59 ` Oliver Sang
2023-11-01 16:59 ` Liam R. Howlett
2023-11-03 2:37 ` Oliver Sang [this message]
2023-10-09 20:16 ` [PATCH 3/3] maple_tree: use preallocations in mas_erase() Sidhartha Kumar
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=ZURc3u2BdMWulbpr@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=Liam.Howlett@oracle.com \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
/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.