public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] RISC-V: Add comment for previous change.
Date: Thu, 08 Feb 2018 21:32:00 -0000	[thread overview]
Message-ID: <3f48fe4a95ec0e67b81d5d606762c91ad9a6b799@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 3f48fe4a95ec0e67b81d5d606762c91ad9a6b799 ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 3f48fe4a95ec0e67b81d5d606762c91ad9a6b799

RISC-V: Add comment for previous change.

	bfd/
	* elfnn-riscv.c (riscv_elf_relocate_section): Add comment for previous
	change.


             reply	other threads:[~2018-02-08 21:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-08 21:32 sergiodj+buildbot [this message]
2018-02-08 21:32 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-02-09  0:17 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-02-09  2:05 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-02-09  3:59 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-02-09  4:04 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-02-09  4:18 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-02-09  4:23 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-02-09  4:34 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-02-09  4:36 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-02-09  8:41 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2018-02-09 13:35 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-02-09 14:05 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot

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=3f48fe4a95ec0e67b81d5d606762c91ad9a6b799@gdb-build \
    --to=sergiodj+buildbot@sergiodj.net \
    --cc=gdb-testers@sourceware.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).