Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] where to commit a kernel modification?
Date: Sat, 21 Apr 2012 15:39:41 +0200	[thread overview]
Message-ID: <201204211539.42000.arnout@mind.be> (raw)
In-Reply-To: <CAPEB33z4-PhKHiqw7WZohZ5kph_eieUN7v2QjCJ4SLn==JDOHg@mail.gmail.com>

On Wednesday 18 April 2012 23:16:00 MERCADIER Johann wrote:
>   I would like to brings some modification to the kernel necessary to
> enable headset o/p to produce sound. Without it the twl6040 is not enabled
> as not registered when module is loaded. Where should I commit this?

 Obviously not here :-)

 Where to submit it to depends on where you're making changes.  There
is a script in the kernel source to help you:

./scripts/get_maintainer.pl <patchfile>

or

./scripts/get_maintainer.pl -f <sourcefile>


 Look carefully at the output and consider for each e-mail address if
it is really appropriate.  Common sense is important here.


 Regards,
 Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-04-21 13:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18 21:16 [Buildroot] where to commit a kernel modification? MERCADIER Johann
2012-04-21 13:39 ` Arnout Vandecappelle [this message]
2012-04-21 19:48   ` Ezequiel García
2012-04-24  9:00     ` MERCADIER Johann
2012-04-24 17:48       ` Ezequiel García

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=201204211539.42000.arnout@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /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