From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
hpa@zytor.com, luto@kernel.org, corbet@lwn.net,
linux-doc@vger.kernel.org, kernel-dev@igalia.com,
kernel@gpiccoli.net, Andre Almeida <andrealmeid@igalia.com>,
Fenghua Yu <fenghua.yu@intel.com>,
Joshua Ashton <joshua@froggi.es>, Melissa Wen <mwen@igalia.com>,
Paul Gofman <pgofman@codeweavers.com>,
Pavel Machek <pavel@denx.de>,
Pierre-Loup Griffais <pgriffais@valvesoftware.com>,
Tony Luck <tony.luck@intel.com>,
Zebediah Figura <zfigura@codeweavers.com>
Subject: Re: [PATCH V2] x86/split_lock: Add sysctl to control the misery mode
Date: Mon, 17 Oct 2022 10:57:01 -0300 [thread overview]
Message-ID: <0d9d589e-4f6c-02a4-fb00-b4467e75b47f@igalia.com> (raw)
In-Reply-To: <Y0tz1/pR/s7+j6s+@debian.me>
Thank you Bagas! I see you fixed the documentation in more than one
place, appreciate that.
What's the next step then, re-submit with your fixes, or wait more
feedback perhaps?
If a maintainer plans to pick this one, maybe they can just apply your
fix-up on top of it.
Cheers,
Guilherme
next prev parent reply other threads:[~2022-10-17 13:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 18:05 [PATCH V2] x86/split_lock: Add sysctl to control the misery mode Guilherme G. Piccoli
2022-10-14 18:17 ` André Almeida
2022-10-14 18:20 ` Guilherme G. Piccoli
2022-10-14 18:22 ` André Almeida
2022-10-14 18:26 ` Luck, Tony
2022-10-15 0:19 ` Guilherme G. Piccoli
2022-10-16 3:00 ` Bagas Sanjaya
2022-10-16 12:26 ` Bagas Sanjaya
2022-10-17 13:57 ` Guilherme G. Piccoli [this message]
2022-10-21 16:56 ` Guilherme G. Piccoli
2022-10-21 17:27 ` Dave Hansen
2022-10-21 19:03 ` Guilherme G. Piccoli
2022-10-21 19:07 ` Dave Hansen
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=0d9d589e-4f6c-02a4-fb00-b4467e75b47f@igalia.com \
--to=gpiccoli@igalia.com \
--cc=andrealmeid@igalia.com \
--cc=bagasdotme@gmail.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=joshua@froggi.es \
--cc=kernel-dev@igalia.com \
--cc=kernel@gpiccoli.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=mwen@igalia.com \
--cc=pavel@denx.de \
--cc=pgofman@codeweavers.com \
--cc=pgriffais@valvesoftware.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=zfigura@codeweavers.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox