From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Joel Granados <joel.granados@kernel•org>
Cc: Luis Chamberlain <mcgrof@kernel•org>, Kees Cook <kees@kernel•org>,
Andrew Morton <akpm@linux-foundation•org>,
Feng Tang <feng.tang@linux•alibaba.com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: manual merge of the sysctl tree with the mm-nonmm-unstable tree
Date: Wed, 23 Jul 2025 09:10:28 +1000 [thread overview]
Message-ID: <20250723091028.33fa0ba1@canb.auug.org.au> (raw)
In-Reply-To: <lzabgfj2r5uf4gnmuibx6vhgdddi7bhqv3wj3ty6arnquu4itw@wsj4knxljyv6>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
Hi Joel,
On Tue, 22 Jul 2025 11:58:48 +0200 Joel Granados <joel.granados@kernel•org> wrote:
>
> I double checked these, and they seem ok from the sysctl side.
>
> @Stephen: Do you prefer an actual acknowledgement that everything is
> good? Or would you prefer no answer to these merge conflict advisories?
> I personally, always make sure that things look sane, but always feel
> that sending out the ACK is a bit of a waste.
Yeah, I generally assume everything is OK unless told otherwise, so the
ACK is not necessary. Though sometimes I express my doubt in my own
solution (I might say something like "I fixed it up (I hope/think ...")
and then it is nice to know either way.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-07-22 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 9:00 linux-next: manual merge of the sysctl tree with the mm-nonmm-unstable tree Stephen Rothwell
2025-07-22 9:58 ` Joel Granados
2025-07-22 23:10 ` Stephen Rothwell [this message]
2025-07-31 1:05 ` Stephen Rothwell
2025-08-04 7:53 ` Joel Granados
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=20250723091028.33fa0ba1@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=feng.tang@linux$(echo .)alibaba.com \
--cc=joel.granados@kernel$(echo .)org \
--cc=kees@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mcgrof@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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