Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/5] package/rpi-userland: bump version to 5070cb7f
Date: Fri, 8 Nov 2019 23:17:35 +0100	[thread overview]
Message-ID: <20191108231735.1d2bc178@gmx.net> (raw)
In-Reply-To: <20191107224604.3fbb7261@windsurf>

Hello Thomas,

On Thu, 7 Nov 2019 22:46:04 +0100, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:

> On Thu,  7 Nov 2019 21:23:37 +0100
> Peter Seiderer <ps.report@gmx.net> wrote:
>
> > - rebased 0003-Disable-Werror-everywhere.patch
> > - remove vcfiled support (upstream removed, see [1])
> >
> > [1] https://github.com/raspberrypi/userland/commit/f00a1189b9f8246dc24c45985de599c50b8c62a5
> >
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
>
> This patch doesn't apply properly here:
>
> $ git pwam 1191416
> Applying patch #1191416 using "git am -s"
> Description: [v2,3/5] package/rpi-userland: bump version to 5070cb7f
> Applying: package/rpi-userland: bump version to 5070cb7f
> error: patch failed: package/rpi-userland/0003-Disable-Werror-everywhere.patch:55
> error: package/rpi-userland/0003-Disable-Werror-everywhere.patch: patch does not apply
> Patch failed at 0001 package/rpi-userland: bump version to 5070cb7f
> hint: Use 'git am --show-current-patch' to see the failed patch
> When you have resolved this problem, run "git am --continue".
> If you prefer to skip this patch, run "git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
> 'git am' failed with exit status 128
>
> I have not investigated why.

Mhhh, strange (and once again, I think it happened already before)...

Diff of the original 'git format-patch' version and the Patchwork download
version:

	$ diff -u v2-0003-package-rpi-userland-bump-version-to-5070cb7f.patch v2-3-5-package-rpi-userland-bump-version-to-5070cb7f.patch
[...]
 diff --git a/Config.in.legacy b/Config.in.legacy
 index fcb10b1291..7167b1d60c 100644
 --- a/Config.in.legacy
 +++ b/Config.in.legacy
 @@ -146,6 +146,12 @@ endif
-
+
  comment "Legacy options removed in 2019.11"
-
+
[...]

With '-<space><newline>' against '+<newline>'..., same against
the saved copy returned from the buildroot mailing list...,
seems someone is eating up my spaces...

Will re-try/re-send the patches...

Regards,
Peter

>
> Thomas

  reply	other threads:[~2019-11-08 22:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-07 20:23 [Buildroot] [PATCH v2 1/5] configs/raspberrypi*: bump kernel version to 1.20190925-1 Peter Seiderer
2019-11-07 20:23 ` [Buildroot] [PATCH v2 2/5] package/rpi-firmware: bump " Peter Seiderer
2019-11-07 21:45   ` Thomas Petazzoni
2019-11-07 20:23 ` [Buildroot] [PATCH v2 3/5] package/rpi-userland: bump version to 5070cb7f Peter Seiderer
2019-11-07 21:46   ` Thomas Petazzoni
2019-11-08 22:17     ` Peter Seiderer [this message]
2019-11-09  9:44       ` Peter Seiderer
2019-11-07 20:23 ` [Buildroot] [PATCH v2 4/5] configs/raspberrypi3_64_defconfig: enable device tree overlay support Peter Seiderer
2019-11-07 21:46   ` Thomas Petazzoni
2019-11-07 20:23 ` [Buildroot] [PATCH v2 5/5] configs/raspberrypi3_64_defconfig: use pi3-miniuart-bt device tree overlay Peter Seiderer
2019-11-07 21:45 ` [Buildroot] [PATCH v2 1/5] configs/raspberrypi*: bump kernel version to 1.20190925-1 Thomas Petazzoni

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=20191108231735.1d2bc178@gmx.net \
    --to=ps.report@gmx.net \
    --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