From: Allison Henderson <allison.henderson@oracle.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "rds-devel@oss.oracle.com" <rds-devel@oss.oracle.com>,
Vegard Nossum <vegard.nossum@oracle.com>,
"oberpar@linux.ibm.com" <oberpar@linux.ibm.com>,
Chuck Lever III <chuck.lever@oracle.com>
Subject: Re: [RFC net-next 1/3] .gitignore: add .gcda files
Date: Sun, 9 Jun 2024 18:08:21 +0000 [thread overview]
Message-ID: <aeb176fa6781f7004b705ddecf1b02744be4f8fb.camel@oracle.com> (raw)
In-Reply-To: <20240607003631.32484-2-allison.henderson@oracle.com>
On Thu, 2024-06-06 at 17:36 -0700, allison.henderson@oracle.com wrote:
+cc Chuck Lever, Peter Oberparleiter, Vegard Nossum, rds-devel
> From: Vegard Nossum <vegard.nossum@oracle.com>
>
> These files contain the runtime coverage data generated by gcov.
>
> Signed-off-by: Vegard Nossum <vegard.nossum@oracle.com>
> Reviewed-by: Allison Henderson <allison.henderson@oracle.com>
> Reviewed-by: Chuck Lever <chuck.lever@oracle.com>
> Signed-off-by: Allison Henderson <allison.henderson@oracle.com>
> ---
> .gitignore | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/.gitignore b/.gitignore
> index c59dc60ba62e..8ff1b4138c56 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -24,6 +24,7 @@
> *.dwo
> *.elf
> *.gcno
> +*.gcda
> *.gz
> *.i
> *.ko
next prev parent reply other threads:[~2024-06-09 18:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 0:36 [RFC net-next 0/3] selftests: rds selftest allison.henderson
2024-06-07 0:36 ` [RFC net-next 1/3] .gitignore: add .gcda files allison.henderson
2024-06-09 18:08 ` Allison Henderson [this message]
2024-06-07 0:36 ` [RFC net-next 2/3] net: rds: add option for GCOV profiling allison.henderson
2024-06-09 18:08 ` Allison Henderson
2024-06-07 0:36 ` [RFC net-next 3/3] selftests: rds: add testing infrastructure allison.henderson
2024-06-07 20:24 ` Simon Horman
2024-06-09 18:08 ` Allison Henderson
2024-06-09 18:08 ` [RFC net-next 0/3] selftests: rds selftest Allison Henderson
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=aeb176fa6781f7004b705ddecf1b02744be4f8fb.camel@oracle.com \
--to=allison.henderson@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=oberpar@linux.ibm.com \
--cc=rds-devel@oss.oracle.com \
--cc=vegard.nossum@oracle.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;
as well as URLs for NNTP newsgroup(s).