From: Christian Lamparter <chunkeey@googlemail.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: "Xose Vazquez Perez" <xose.vazquez@gmail.com>,
"David Woodhouse" <dwmw2@infradead.org>,
"Dan Horák" <dan@danny.cz>,
linux-wireless <linux-wireless@vger.kernel.org>,
"Stefan Lippers-Hollmann" <s.L-H@gmx.de>
Subject: Re: [PATCH] linux-firmware: add carl9170 firmware
Date: Fri, 18 Jan 2013 00:52:06 +0100 [thread overview]
Message-ID: <201301180052.07145.chunkeey@googlemail.com> (raw)
In-Reply-To: <1358458004.15692.147.camel@deadeye.wl.decadent.org.uk>
On Thursday, January 17, 2013 10:26:44 PM Ben Hutchings wrote:
> On Tue, 2013-01-15 at 23:50 +0100, Xose Vazquez Perez wrote:
> > On 01/14/2013 12:27 PM, Ben Hutchings wrote:
> >
> > > OK, I've worked this out now: there are two post-processing steps
> > > required, one of which is done by './autogen.sh install', and one of
> > > which (add a checksum) is not done at all. I've added that step to it
> > > and can now rebuild a bit-identical image.
> > >
> > > So I've applied this, made a few fixes, and pushed.
> >
> > Sorry, I took half sabbatical. Now cleaning inbox.
> >
> > I believe Christian releases a new version(1.9.7) recently,
> > and I did send 1.9.6 months ago. It should be updated.
Depends. [This would be another question... what qualifies for
a new push to linux-firmware? Should there be one for every
series-of-related-patches? release e.g.: 1.9.7, 1.9.8? Or after
the firmware passed the test of time?]
Anyway, the biggest 'new thing' in 1.9.7 was getting "Link Time
Optimization" ready [1].
> I'm happy to take either a single patch for the new release or
> one patch for each commit in your repository, whichever you prefer.
Would it be possible to attach a carl9170fw-x.y.z-source.tar.xz/bz2/gz/zip
along the carl9170-1.fw binary instead of the source dump in carl9170fw/?
I've picked up all of Ben's carl9170fw patches and added them into
carl9170fw-master. So in theory we are good to go.
Regards
Christian
[1] <https://github.com/chunkeey/carl9170fw/commit/1a2fbaf4f621cbb37f36637b1d4101f453474f7a>
next prev parent reply other threads:[~2013-01-17 23:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1342353398-3147-1-git-send-email-xose.vazquez@gmail.com>
[not found] ` <1342666598.11373.97.camel@deadeye.wl.decadent.org.uk>
[not found] ` <1358162875.15692.14.camel@deadeye.wl.decadent.org.uk>
2013-01-15 22:50 ` [PATCH] linux-firmware: add carl9170 firmware Xose Vazquez Perez
2013-01-17 21:26 ` Ben Hutchings
2013-01-17 23:52 ` Christian Lamparter [this message]
2013-02-18 3:15 ` Ben Hutchings
2013-02-18 14:42 ` Christian Lamparter
2012-07-14 18:46 Xose Vazquez Perez
2012-07-14 19:58 ` Ben Hutchings
2012-07-14 20:50 ` Xose Vazquez Perez
2012-07-14 21:06 ` Ben Hutchings
-- strict thread matches above, loose matches on Subject: below --
2012-07-14 18:44 Xose Vazquez Perez
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=201301180052.07145.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=ben@decadent.org.uk \
--cc=dan@danny.cz \
--cc=dwmw2@infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=s.L-H@gmx.de \
--cc=xose.vazquez@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).