All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org <patchwork-bot+linux-riscv@kernel.org>
To: kvm-riscv@lists.infradead.org
Subject: [PATCH] KVM: selftest: Define _GNU_SOURCE for all selftests code
Date: Wed, 22 May 2024 23:32:23 +0000	[thread overview]
Message-ID: <171642074371.9409.16238055569874422523.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240423190308.2883084-1-seanjc@google.com>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Sean Christopherson <seanjc@google.com>:

On Tue, 23 Apr 2024 12:03:08 -0700 you wrote:
> Define _GNU_SOURCE is the base CFLAGS instead of relying on selftests to
> manually #define _GNU_SOURCE, which is repetitive and error prone.  E.g.
> kselftest_harness.h requires _GNU_SOURCE for asprintf(), but if a selftest
> includes kvm_test_harness.h after stdio.h, the include guards result in
> the effective version of stdio.h consumed by kvm_test_harness.h not
> defining asprintf():
> 
> [...]

Here is the summary with links:
  - KVM: selftest: Define _GNU_SOURCE for all selftests code
    https://git.kernel.org/riscv/c/730cfa45b5f4

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html




WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Sean Christopherson <seanjc@google.com>
Cc: linux-riscv@lists.infradead.org, pbonzini@redhat.com,
	maz@kernel.org, oliver.upton@linux.dev, anup@brainfault.org,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, borntraeger@linux.ibm.com,
	frankja@linux.ibm.com, imbrenda@linux.ibm.com,
	kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.linux.dev, kvm-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org, usama.anjum@collabora.com
Subject: Re: [PATCH] KVM: selftest: Define _GNU_SOURCE for all selftests code
Date: Wed, 22 May 2024 23:32:23 +0000	[thread overview]
Message-ID: <171642074371.9409.16238055569874422523.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240423190308.2883084-1-seanjc@google.com>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Sean Christopherson <seanjc@google.com>:

On Tue, 23 Apr 2024 12:03:08 -0700 you wrote:
> Define _GNU_SOURCE is the base CFLAGS instead of relying on selftests to
> manually #define _GNU_SOURCE, which is repetitive and error prone.  E.g.
> kselftest_harness.h requires _GNU_SOURCE for asprintf(), but if a selftest
> includes kvm_test_harness.h after stdio.h, the include guards result in
> the effective version of stdio.h consumed by kvm_test_harness.h not
> defining asprintf():
> 
> [...]

Here is the summary with links:
  - KVM: selftest: Define _GNU_SOURCE for all selftests code
    https://git.kernel.org/riscv/c/730cfa45b5f4

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Sean Christopherson <seanjc@google.com>
Cc: linux-riscv@lists.infradead.org, pbonzini@redhat.com,
	maz@kernel.org, oliver.upton@linux.dev, anup@brainfault.org,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, borntraeger@linux.ibm.com,
	frankja@linux.ibm.com, imbrenda@linux.ibm.com,
	kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.linux.dev, kvm-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org, usama.anjum@collabora.com
Subject: Re: [PATCH] KVM: selftest: Define _GNU_SOURCE for all selftests code
Date: Wed, 22 May 2024 23:32:23 +0000	[thread overview]
Message-ID: <171642074371.9409.16238055569874422523.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240423190308.2883084-1-seanjc@google.com>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Sean Christopherson <seanjc@google.com>:

On Tue, 23 Apr 2024 12:03:08 -0700 you wrote:
> Define _GNU_SOURCE is the base CFLAGS instead of relying on selftests to
> manually #define _GNU_SOURCE, which is repetitive and error prone.  E.g.
> kselftest_harness.h requires _GNU_SOURCE for asprintf(), but if a selftest
> includes kvm_test_harness.h after stdio.h, the include guards result in
> the effective version of stdio.h consumed by kvm_test_harness.h not
> defining asprintf():
> 
> [...]

Here is the summary with links:
  - KVM: selftest: Define _GNU_SOURCE for all selftests code
    https://git.kernel.org/riscv/c/730cfa45b5f4

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Sean Christopherson <seanjc@google.com>
Cc: linux-riscv@lists.infradead.org, pbonzini@redhat.com,
	maz@kernel.org, oliver.upton@linux.dev, anup@brainfault.org,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, borntraeger@linux.ibm.com,
	frankja@linux.ibm.com, imbrenda@linux.ibm.com,
	kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.linux.dev, kvm-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org, usama.anjum@collabora.com
Subject: Re: [PATCH] KVM: selftest: Define _GNU_SOURCE for all selftests code
Date: Wed, 22 May 2024 23:32:23 +0000	[thread overview]
Message-ID: <171642074371.9409.16238055569874422523.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240423190308.2883084-1-seanjc@google.com>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Sean Christopherson <seanjc@google.com>:

On Tue, 23 Apr 2024 12:03:08 -0700 you wrote:
> Define _GNU_SOURCE is the base CFLAGS instead of relying on selftests to
> manually #define _GNU_SOURCE, which is repetitive and error prone.  E.g.
> kselftest_harness.h requires _GNU_SOURCE for asprintf(), but if a selftest
> includes kvm_test_harness.h after stdio.h, the include guards result in
> the effective version of stdio.h consumed by kvm_test_harness.h not
> defining asprintf():
> 
> [...]

Here is the summary with links:
  - KVM: selftest: Define _GNU_SOURCE for all selftests code
    https://git.kernel.org/riscv/c/730cfa45b5f4

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2024-05-22 23:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23 19:03 [PATCH] KVM: selftest: Define _GNU_SOURCE for all selftests code Sean Christopherson
2024-04-23 19:03 ` Sean Christopherson
2024-04-23 19:03 ` Sean Christopherson
2024-04-23 19:03 ` Sean Christopherson
2024-04-23 19:05 ` Muhammad Usama Anjum
2024-04-23 19:05   ` Muhammad Usama Anjum
2024-04-23 19:05   ` Muhammad Usama Anjum
2024-04-23 19:05   ` Muhammad Usama Anjum
2024-04-24  5:53 ` Anup Patel
2024-04-24  5:53   ` Anup Patel
2024-04-24  5:53   ` Anup Patel
2024-04-24  5:53   ` Anup Patel
2024-04-24  8:34 ` Claudio Imbrenda
2024-04-24  8:34   ` Claudio Imbrenda
2024-04-24  8:34   ` Claudio Imbrenda
2024-04-24  8:34   ` Claudio Imbrenda
2024-04-25 22:41 ` Oliver Upton
2024-04-25 22:41   ` Oliver Upton
2024-04-25 22:41   ` Oliver Upton
2024-04-25 22:41   ` Oliver Upton
2024-04-29 20:45 ` Sean Christopherson
2024-04-29 20:45   ` Sean Christopherson
2024-04-29 20:45   ` Sean Christopherson
2024-04-29 20:45   ` Sean Christopherson
2024-05-22 23:32 ` patchwork-bot+linux-riscv [this message]
2024-05-22 23:32   ` patchwork-bot+linux-riscv
2024-05-22 23:32   ` patchwork-bot+linux-riscv
2024-05-22 23:32   ` patchwork-bot+linux-riscv

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=171642074371.9409.16238055569874422523.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=kvm-riscv@lists.infradead.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 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.