From: Johannes Berg <johannes@sipsolutions.net>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
backports@vger.kernel.org
Subject: Re: [PATCH RFC 2/2] add script to enable audio backport
Date: Fri, 18 Sep 2015 15:11:22 +0200 [thread overview]
Message-ID: <1442581882.2168.13.camel@sipsolutions.net> (raw)
In-Reply-To: <55FC0C72.20806@linux.intel.com>
On Fri, 2015-09-18 at 08:06 -0500, Pierre-Louis Bossart wrote:
>
> "You can submit this part upstream btw - it'll just be disabled in
> the
> default copy-list... unless you also submit that upstream"
>
> If you are ok to take the patches and have the upstream copy-list
> include the sound files then yes the script is not necessary. I just
> wanted to have a first pass that isn't intrusive or breaks all the
> backports, but simple enough for others to try and test.
Ah. Well I think that we'd probably wait until it compiles against all
kernels, but after that having them included in the upstream copy-list
isn't an issue at all.
And until then perhaps you'd just provide it as a separate tree or
patch somewhere, I don't think we should add it to backports like that.
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
prev parent reply other threads:[~2015-09-18 13:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 21:47 [PATCH RFC 0/2] addition of audio to backports Pierre-Louis Bossart
2015-09-17 21:47 ` [PATCH RFC 1/2] Add required changes for audio packports Pierre-Louis Bossart
2015-09-18 7:15 ` Johannes Berg
2015-09-18 13:00 ` Pierre-Louis Bossart
2015-09-18 13:09 ` Johannes Berg
2015-09-17 21:47 ` [PATCH RFC 2/2] add script to enable audio backport Pierre-Louis Bossart
2015-09-18 7:17 ` Johannes Berg
2015-09-18 13:06 ` Pierre-Louis Bossart
2015-09-18 13:11 ` Johannes Berg [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=1442581882.2168.13.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.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.