Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] package/rpi-firmware: improve installation of dtb files
Date: Fri, 16 Mar 2018 14:07:43 +0100	[thread overview]
Message-ID: <878tasgodc.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAFGQKxdXDVU_yWcrsiawYR2-=a7=FAp34=AOqB4EXXTCCyH7sg@mail.gmail.com> (Martin Bark's message of "Fri, 16 Mar 2018 10:52:54 +0000")

>>>>> "Martin" == Martin Bark <martin@barkynet.com> writes:

Hi,

 > For some reason my v2 patch set disappeared into /dev/null in
 > patchwork.   I'll include the updates to rpi-wifi-firmware and submit
 > a v3 patchset.

We unfortunately have some reliability issues with patchwork at the
moment - Thanks for sending v3.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2018-03-16 13:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 13:24 [Buildroot] [PATCH 1/4] package/rpi-firmware: bump version Martin Bark
2018-03-15 13:24 ` [Buildroot] [PATCH 2/4] configs/raspberrypi*: bump kernel version Martin Bark
2018-03-15 13:24 ` [Buildroot] [PATCH 3/4] board/raspberrypi: add support for rpi3 b+ Martin Bark
2018-03-15 13:33   ` Baruch Siach
2018-03-15 14:07     ` Martin Bark
2018-03-15 13:24 ` [Buildroot] [PATCH 4/4] package/rpi-firmware: improve installation of dtb files Martin Bark
2018-03-15 19:40   ` Peter Seiderer
2018-03-15 19:58     ` Martin Bark
2018-03-15 21:59       ` Yann E. MORIN
2018-03-15 22:40         ` Martin Bark
2018-03-16  9:32           ` Jens Maus
2018-03-16 10:52             ` Martin Bark
2018-03-16 13:07               ` Peter Korsgaard [this message]
2018-03-16 13:12               ` Jens Maus
2018-03-16 18:08                 ` Martin Bark
2018-03-15 19:28 ` [Buildroot] [PATCH 1/4] package/rpi-firmware: bump version Peter Seiderer
2018-03-15 20:23   ` Martin Bark

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=878tasgodc.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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