All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 18 Feb 2013 15:42:05 +0100	[thread overview]
Message-ID: <201302181542.05471.chunkeey@googlemail.com> (raw)
In-Reply-To: <1361157348.5374.538.camel@deadeye.wl.decadent.org.uk>

On Monday, February 18, 2013 04:15:48 AM Ben Hutchings wrote:
> Sorry for the delay in replying to this.
I see. Well, thanks for the response.

> On Fri, 2013-01-18 at 00:52 +0100, Christian Lamparter wrote:
> > On Thursday, January 17, 2013 10:26:44 PM Ben Hutchings wrote:
> > > 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/?
> 
> Perhaps, but what would be the benefit?
Actually, I was thinking that having a single source.tar would be easier
to handle and it would cause less clutter (Yeah, I've seen people do cp -r
linux-firmware.git/* into /lib/firmware/. And in this case - I think - a
source.tar.xyz is less of an eyesore...). Also a single source.tar can be
easily signed and verified. But of course, it's your tree and therefore
it's your call.

[Note: Unless there is a bug that needs to be fixed ASAP, I'll wait for
gcc 4.8 to be ready before I make carl9170fw 1.9.8. So, there is plenty
of time to decide what to do.]

Regards
	Christian

  reply	other threads:[~2013-02-18 14:42 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
2013-02-18  3:15           ` Ben Hutchings
2013-02-18 14:42             ` Christian Lamparter [this message]
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=201302181542.05471.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.