public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Beyer <mail@beyermatthias.de>
To: linux-kernel@vger.kernel.org
Subject: Re: How to test my patches for the (staging) android driver?
Date: Tue, 3 Dec 2013 16:57:08 +0100	[thread overview]
Message-ID: <20131203155708.GD2264@fu> (raw)
In-Reply-To: <20131203151642.GB2264@fu>

[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]

Hi,

Greg-KHs email bot tells me to send this message to a ML. It suggests
to send it to this list or kernelnewbies@nl.linux.org, but the latter
results in a failure notice. So I send this email to this list.

On 03-12-2013 16:16:42, Matthias Beyer wrote:
> Hi,
> 
> First: I'm really new to the kernel in manner of submitting patches,
> testing etc. Please, if you send me guidelines or pointers on
> what to do, explain how to do things!
> 
> I'm working on some cleanup patches for code in drivers/staging/android/.
> These patches are cleanup patches as suggested in the appropriate TODO
> file, including fixes for checkpatch, but also function splitting as
> there are some really long functions (mainly in binder.c).
> 
> How to test my code beside compiling it? Do I even have a possibility
> to test it or should I just send it to you?
> 
> Besides: Which ML should I post this (and the patches) to? Main Kernel
> ML?
> 
> -- 
> Mit freundlichen Grüßen,
> Kind regards,
> Matthias Beyer
> 
> Proudly sent with mutt.
> Happily signed with gnupg.



-- 
Mit freundlichen Grüßen,
Kind regards,
Matthias Beyer

Proudly sent with mutt.
Happily signed with gnupg.

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

           reply	other threads:[~2013-12-03 16:04 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20131203151642.GB2264@fu>]

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=20131203155708.GD2264@fu \
    --to=mail@beyermatthias.de \
    --cc=linux-kernel@vger.kernel.org \
    /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