From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] linux-firmware: bump version
Date: Thu, 10 Dec 2015 21:52:14 +0100 [thread overview]
Message-ID: <87fuzajabl.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1449756107-9441-1-git-send-email-john@keeping.me.uk> (John Keeping's message of "Thu, 10 Dec 2015 14:01:46 +0000")
>>>>> "John" == John Keeping <john@keeping.me.uk> writes:
> From: John Keeping <john@metanate.com>
> CXGB4 firmware files have been renamed upstream.
> Signed-off-by: John Keeping <john@metanate.com>
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2015-12-10 20:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 14:01 [Buildroot] [PATCH 1/2] linux-firmware: bump version John Keeping
2015-12-10 14:01 ` [Buildroot] [PATCH 2/2] linux-firmware: update Broadcom 43xx file list John Keeping
2015-12-10 20:52 ` Peter Korsgaard
2015-12-10 20:55 ` Yann E. MORIN
2015-12-10 20:52 ` Peter Korsgaard [this message]
2015-12-10 20:53 ` [Buildroot] [PATCH 1/2] linux-firmware: bump version Yann E. MORIN
-- strict thread matches above, loose matches on Subject: below --
2016-10-28 2:54 [Buildroot] [PATCH 1/2] linux-firmware: Bump version Joel Stanley
2016-10-28 12:45 ` 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=87fuzajabl.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