public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Reuben Thomas <rrt@sc3d.org>
To: gdb-patches@sourceware.org
Subject: A couple of trivial fixes
Date: Sat, 2 Jan 2021 12:16:06 +0000	[thread overview]
Message-ID: <CAOnWdoiJSmCxtAwz3juuid_1xoyk-+pxiC1=egnRwhFSCxhxng@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 244 bytes --]

I attach a couple of patches against master as of just now, one to fix the
English in a comment, and the other to remove gdb_select.h from
gdb/Makefile.in, as it has been moved to gdbsupport/ (this broke "make
tags").

-- 
https://rrt.sc3d.org

[-- Attachment #2: 0001-binutils-readelf.c-Fix-English-in-comment.patch --]
[-- Type: text/x-patch, Size: 948 bytes --]

From 1163b03a6569d63915a24fa12e3f2e0a30910672 Mon Sep 17 00:00:00 2001
From: Reuben Thomas <rrt@sc3d.org>
Date: Sat, 2 Jan 2021 11:48:09 +0000
Subject: [PATCH 1/2] binutils/readelf.c: Fix English in comment

---
 binutils/readelf.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/binutils/readelf.c b/binutils/readelf.c
index d6e7a7b3835..ad16b4571c9 100644
--- a/binutils/readelf.c
+++ b/binutils/readelf.c
@@ -2609,7 +2609,7 @@ static void
 decode_ARC_machine_flags (unsigned e_flags, unsigned e_machine, char buf[])
 {
   /* ARC has two machine types EM_ARC_COMPACT and EM_ARC_COMPACT2.  Some
-     other compilers don't a specific architecture type in the e_flags, and
+     other compilers don't specify an architecture type in the e_flags, and
      instead use EM_ARC_COMPACT for old ARC600, ARC601, and ARC700
      architectures, and switch to EM_ARC_COMPACT2 for newer ARCEM and ARCHS
      architectures.
-- 
2.25.1


[-- Attachment #3: 0002-gdb-Makefile.in-remove-gdb_select.h-moved-to-gdbsupp.patch --]
[-- Type: text/x-patch, Size: 588 bytes --]

From a996b3e006d6e082b486d48bdbab51e018793c19 Mon Sep 17 00:00:00 2001
From: Reuben Thomas <rrt@sc3d.org>
Date: Sat, 2 Jan 2021 12:09:27 +0000
Subject: [PATCH 2/2] gdb/Makefile.in: remove gdb_select.h, moved to gdbsupport

---
 gdb/Makefile.in | 1 -
 1 file changed, 1 deletion(-)

diff --git a/gdb/Makefile.in b/gdb/Makefile.in
index 9267bea7beb..3fdcb337cc4 100644
--- a/gdb/Makefile.in
+++ b/gdb/Makefile.in
@@ -1298,7 +1298,6 @@ HFILES_NO_SRCDIR = \
 	gdb_obstack.h \
 	gdb_proc_service.h \
 	gdb_regex.h \
-	gdb_select.h \
 	gdb-stabs.h \
 	gdb_vfork.h \
 	gdb_wchar.h \
-- 
2.25.1


             reply	other threads:[~2021-01-02 12:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-02 12:16 Reuben Thomas [this message]
2021-01-04 19:33 ` Tom Tromey
2021-01-06 21:46   ` Reuben Thomas
2022-03-22 22:10     ` Reuben Thomas
2022-03-23 10:50       ` [PATCHv2 0/3] Fix for 'make tags' build rule Andrew Burgess
2022-03-23 10:50         ` [PATCHv2 1/3] gdb/Makefile.in: remove SOURCES variable Andrew Burgess
2022-03-23 10:50         ` [PATCHv2 2/3] gdb/Makefile.in: fix 'make tags' build target Andrew Burgess
2022-03-23 10:50         ` [PATCHv2 3/3] gdb/Makefile.in: move ALLDEPFILES earlier in Makefile.in Andrew Burgess
2022-04-03 14:50         ` [PATCHv2 0/3] Fix for 'make tags' build rule Andrew Burgess

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='CAOnWdoiJSmCxtAwz3juuid_1xoyk-+pxiC1=egnRwhFSCxhxng@mail.gmail.com' \
    --to=rrt@sc3d.org \
    --cc=gdb-patches@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).