From: David Woodhouse <dwmw2@infradead.org>
To: Dave <kilroyd@googlemail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux-firmware patches
Date: Wed, 08 Oct 2008 11:29:46 +0100 [thread overview]
Message-ID: <1223461786.20499.29.camel@pmac.infradead.org> (raw)
In-Reply-To: <48EBAC11.7060803@gmail.com>
On Tue, 2008-10-07 at 19:36 +0100, Dave wrote:
> Should patches to add firmware to the linux-firmware tree (and not the
> main kernel) be sent to linux-kernel, or somewhere else? It wasn't
> mentioned in the [ANNOUNCE]*, and I haven't been able to find an
> example on list.
>
> Just wanted to check before posting an 80k patch consisting of non-GPL
> binary files.
Patches with binary files are going to be hard -- probably best just to
commit to a git tree and ask me to pull. Or mail the files separately,
with the changes to the WHENCE file as a separate patch.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
prev parent reply other threads:[~2008-10-08 10:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 18:36 Dave
2008-10-08 10:29 ` David Woodhouse [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=1223461786.20499.29.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=kilroyd@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®