All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@buildroot.org
Subject: [Buildroot] [git commit] package/gcc: fix check-package warnings in patches
Date: Tue, 6 Sep 2022 21:55:51 +0200	[thread overview]
Message-ID: <20220906194101.6A77D821CC@busybox.osuosl.org> (raw)

commit: https://git.buildroot.net/buildroot/commit/?id=4124d47b0b517c13d55e3ec738070f3cd24d1ac8
branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master

package/gcc/11.3.0/0005-rs6000-Improve-.machine.patch:4: generate your patches with 'git format-patch -N'
package/gcc/11.3.0/0006-rs6000-Do-not-use-rs6000_cpu-for-.machine-ppc-and-pp.patch:4: generate your patches with 'git format-patch -N'

Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
---
 package/gcc/11.3.0/0005-rs6000-Improve-.machine.patch                   | 2 +-
 .../0006-rs6000-Do-not-use-rs6000_cpu-for-.machine-ppc-and-pp.patch     | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/package/gcc/11.3.0/0005-rs6000-Improve-.machine.patch b/package/gcc/11.3.0/0005-rs6000-Improve-.machine.patch
index 6107900736..82a667ab7b 100644
--- a/package/gcc/11.3.0/0005-rs6000-Improve-.machine.patch
+++ b/package/gcc/11.3.0/0005-rs6000-Improve-.machine.patch
@@ -1,7 +1,7 @@
 From ca2c3a7d3db7a699c358d3408f820396dd536fc8 Mon Sep 17 00:00:00 2001
 From: Segher Boessenkool <segher@kernel.crashing.org>
 Date: Tue, 1 Mar 2022 17:04:29 +0000
-Subject: [PATCH 5/6] rs6000: Improve .machine
+Subject: [PATCH] rs6000: Improve .machine
 
 This adds more correct .machine for most older CPUs.  It should be
 conservative in the sense that everything we handled before we handle at
diff --git a/package/gcc/11.3.0/0006-rs6000-Do-not-use-rs6000_cpu-for-.machine-ppc-and-pp.patch b/package/gcc/11.3.0/0006-rs6000-Do-not-use-rs6000_cpu-for-.machine-ppc-and-pp.patch
index d2335cd689..43fed4c19f 100644
--- a/package/gcc/11.3.0/0006-rs6000-Do-not-use-rs6000_cpu-for-.machine-ppc-and-pp.patch
+++ b/package/gcc/11.3.0/0006-rs6000-Do-not-use-rs6000_cpu-for-.machine-ppc-and-pp.patch
@@ -1,7 +1,7 @@
 From 6de33ed642f119f1e2543095dd56e4a94f97c27f Mon Sep 17 00:00:00 2001
 From: Segher Boessenkool <segher@kernel.crashing.org>
 Date: Fri, 11 Mar 2022 21:15:18 +0000
-Subject: [PATCH 6/6] rs6000: Do not use rs6000_cpu for .machine ppc and ppc64
+Subject: [PATCH] rs6000: Do not use rs6000_cpu for .machine ppc and ppc64
  (PR104829)
 
 Fixes: 77eccbf39ed5
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2022-09-06 19:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06 19:55 Arnout Vandecappelle [this message]
2022-09-18  9:01 ` [Buildroot] [git commit] package/gcc: fix check-package warnings in patches Peter Korsgaard

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=20220906194101.6A77D821CC@busybox.osuosl.org \
    --to=arnout@mind.be \
    --cc=buildroot@buildroot.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.