Linux backports project
 help / color / mirror / Atom feed
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 09:17:13 +0200	[thread overview]
Message-ID: <1442560633.2168.6.camel@sipsolutions.net> (raw)
In-Reply-To: <1442526437-22392-3-git-send-email-pierre-louis.bossart@linux.intel.com> (sfid-20150917_234743_628456_B160EAFA)

On Thu, 2015-09-17 at 16:47 -0500, Pierre-Louis Bossart wrote:
> bash enable_audio.sh will add the required files in copylist
> and patch some of the backport headers
> 
I don't think this should be part of backports - the code modifications
shouldn't be necessary, you can add everything to copy-list as it
should be (and run with your own copy-list for just sound), and provide
a defconfig file.

Scripting really shouldn't be there I think.

johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in

  reply	other threads:[~2015-09-18  7:17 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 [this message]
2015-09-18 13:06     ` Pierre-Louis Bossart
2015-09-18 13:11       ` Johannes Berg

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=1442560633.2168.6.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox