From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] binutils: Fix glibc building for ARC with stock binutils 2.30
Date: Wed, 13 Jun 2018 23:34:10 +0200 [thread overview]
Message-ID: <20180613233410.23a34cd9@windsurf> (raw)
In-Reply-To: <c2d3f37ce30daa17d69e64d3ced5bf8df803cd09.camel@synopsys.com>
Hello,
On Wed, 13 Jun 2018 21:16:57 +0000, Alexey Brodkin wrote:
> > I've applied to master after:
> >
> > - Removing the number from the patch titles (use 'git format-patch -N'
> > please!)
>
> Was it something we used to do before?
Yes, that's not new. I believe it's even written in the Buildroot
manual.
> > - Adjusting the numbering of patch file names. Recently, Romain Naour
> > renumbered all patches and made them Git formatted, so it would be
> > nice to keep that consistency.
>
> I intentionally started from 10 so that a couple of more generic patches might be
> squeezed before ARC-specific ones. But will keep in mind your preference for next
> submissions.
Yeah, we used to do that for gcc/binutils indeed, but it was a bit
messy. Romain switched to a regular numbering as generated by git
format-patch, which I believe makes sense.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-06-13 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 16:39 [Buildroot] [PATCH] binutils: Fix glibc building for ARC with stock binutils 2.30 Alexey Brodkin
2018-06-13 20:29 ` Thomas Petazzoni
2018-06-13 21:16 ` Alexey Brodkin
2018-06-13 21:34 ` Thomas Petazzoni [this message]
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=20180613233410.23a34cd9@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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