> Add the opcode used by WRMSRNS, which is the non-serializing version of
> WRMSR and may replace it to improve performance, to the x86 opcode map.
>
> Tested-by: Shan Kang
> Signed-off-by: Xin Li
> Acked-by: Masami Hiramatsu (Google)
Hi Masami,
Boris prefers to merge the first 3 patches into
On Wed, Nov 29, 2023 at 09:07:01PM +0530, Attreyee M wrote:
> Respected Maintainers,
>
> Please give me some time to make the changes again.
> I will be making the changes in a day.
>
Please don't top-post; reply inline with appropriate context instead.
OK, see you in v2! Don't forget to Cc: me
On Wed, Nov 29, 2023 at 03:26:18PM +, Matthew Wilcox wrote:
> On Wed, Nov 29, 2023 at 07:29:35AM -0700, Jonathan Corbet wrote:
> > Bagas Sanjaya writes:
> >
> > > I was prompted to write this little grammar fix series when reading
> > > the fix from Attreyee [1], with review comments requesti
On Thu, Nov 30, 2023 at 06:58:16AM +0700, Bagas Sanjaya wrote:
> I do this posting because I thought the OP (Attreyee) didn't respond in
> timely manner (just like random Chinese contributors like @cdjrlc.com
> and @208suo.com people).
That's a ridiculous excuse. The original posting was two days
On 11/29/23 20:53, Joe Lawrence wrote:
> On 11/29/23 08:25, Bagas Sanjaya wrote:
>> I was prompted to write this little grammar fix series when reading
>> the fix from Attreyee [1], with review comments requesting changes
>> to that fix. So here's my version of the fix, with reviews from [1]
>> add
On Wed, Nov 29, 2023 at 04:11:00PM +, Matthew Wilcox wrote:
> On Tue, Nov 28, 2023 at 09:24:00PM -0800, Darrick J. Wong wrote:
> > Actually, ignore this suggestion. I forgot that I have vim paths
> > trained on the Documentation/filesystems/ directory, which means I'll
> > lose the ability to
On Wed, Nov 29, 2023 at 07:39:47PM +0700, Bagas Sanjaya wrote:
> XFS docs are currently in upper-level Documentation/filesystems.
> Although these are currently 4 docs, they are already outstanding as
> a group and can be moved to its own subdirectory.
>
> Consolidate them into Documentation/files
On Wed, Nov 29, 2023 at 07:29:35AM -0700, Jonathan Corbet wrote:
> Bagas Sanjaya writes:
>
> > I was prompted to write this little grammar fix series when reading
> > the fix from Attreyee [1], with review comments requesting changes
> > to that fix. So here's my version of the fix, with reviews
On 11/29/23 05:08, Miroslav Benes wrote:
>
> I am not a native speaker, but "step on each other's toe" sounds the best
> to me. Or perhaps even "they need to be aware of each other and not step
> on their toes" since it is then kind of implied? English is difficult :).
>
Native speaker here, s
Bagas Sanjaya writes:
> I was prompted to write this little grammar fix series when reading
> the fix from Attreyee [1], with review comments requesting changes
> to that fix. So here's my version of the fix, with reviews from [1]
> addressed (and distinct grammar fixes splitted).
How is this he
On 11/29/23 08:25, Bagas Sanjaya wrote:
> I was prompted to write this little grammar fix series when reading
> the fix from Attreyee [1], with review comments requesting changes
> to that fix. So here's my version of the fix, with reviews from [1]
> addressed (and distinct grammar fixes splitted).
I was prompted to write this little grammar fix series when reading
the fix from Attreyee [1], with review comments requesting changes
to that fix. So here's my version of the fix, with reviews from [1]
addressed (and distinct grammar fixes splitted).
[1]: https://lore.kernel.org/lkml/202311271557
The opposite action of releasing locks is acquiring them, not getting
them (as in configuration options; the inverse of such action is
setting options). Correct it.
Signed-off-by: Bagas Sanjaya
---
Documentation/livepatch/livepatch.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
On Wed, Nov 29, 2023 at 11:08:46AM +0100, Miroslav Benes wrote:
> On Tue, 28 Nov 2023, Randy Dunlap wrote:
>
> >
> >
> > On 11/28/23 06:12, Matthew Wilcox wrote:
> > > On Mon, Nov 27, 2023 at 11:41:31AM -0800, Randy Dunlap wrote:
> > >> Hi,
> > >>
> > >> On 11/27/23 07:57, attreyee-muk wrote:
>
On Wed, Nov 29, 2023 at 11:19:15AM +0100, Krzysztof Kozlowski wrote:
> On 29/11/2023 08:29, Francesco Dolcini wrote:
> > On Sat, Nov 25, 2023 at 07:44:22PM +0100, Krzysztof Kozlowski wrote:
> >> ---
> >> +Following order of properties in device nodes is preferred:
> >> +
> >> +1. compatible
> >> +2
On 28/11/2023 21:00, Dragan Simic wrote:
>> 5. Allow two style of ordering overrides in board DTS: alphabetically
>> or
>>by order of DTSI (Rob).
>> 6. I did not incorporate feedback about, due to lack of consensus and
>> my
>>disagreement:
>>a. SoM being DTS without DTSI in "Organizi
On 29/11/2023 08:29, Francesco Dolcini wrote:
> On Sat, Nov 25, 2023 at 07:44:22PM +0100, Krzysztof Kozlowski wrote:
>> Document preferred coding style for Devicetree sources (DTS and DTSI),
>> to bring consistency among all (sub)architectures and ease in reviews.
>
> Thank Krzysztof, we had most
On 27/11/2023 15:19, Geert Uytterhoeven wrote:
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/dts-coding-style.rst
>
>> + /* SoC DTSI */
>> +
>> + / {
>> + cpus {
>> + /* ... */
>> + };
>> +
>> + psci {
>> +
Hi Francesco,
On Wed, Nov 29, 2023 at 8:29 AM Francesco Dolcini wrote:
> On Sat, Nov 25, 2023 at 07:44:22PM +0100, Krzysztof Kozlowski wrote:
> > Document preferred coding style for Devicetree sources (DTS and DTSI),
> > to bring consistency among all (sub)architectures and ease in reviews.
>
> T
19 matches
Mail list logo
