From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] linux-firmware: Added brcm43143 support.
Date: Wed, 22 Jul 2015 22:35:49 +0200 [thread overview]
Message-ID: <20150722223549.41a8a710@free-electrons.com> (raw)
In-Reply-To: <1437588847-23802-1-git-send-email-jordan@yelloz.me>
Dear Jordan Yelloz,
On Wed, 22 Jul 2015 11:14:07 -0700, Jordan Yelloz wrote:
> Signed-off-by: Jordan Yelloz <jordan@yelloz.me>
> ---
> package/linux-firmware/linux-firmware.mk | 1 +
> 1 file changed, 1 insertion(+)
We normally require patches to be sent inline and not as attachments:
you should use git send-email to send the patches.
But since your patch was trivial and didn't require a lot of review, I
applied it as is.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-07-22 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 18:14 [Buildroot] [PATCH 1/1] linux-firmware: Added brcm43143 support Jordan Yelloz
2015-07-22 20:35 ` 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=20150722223549.41a8a710@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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