From: dev@snitselaar.org (Jerry Snitselaar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: first patch
Date: Sun, 27 Dec 2015 15:28:10 -0700 [thread overview]
Message-ID: <20151227222810.GA24677@rhwork.redhat.com> (raw)
In-Reply-To: <CAKNa9uAs1AeheG28_PiwQXOMU+VMxr3Wni9tPoRJAzuJ3kkJMA@mail.gmail.com>
On Wed Dec 23 15, maoma king wrote:
> Dear
> I have sent my first patch (https://lkml.org/lkml/2015/11/18/239) to
> linux-next tree.But I never received anything about it.So I sent it
> again. You say "Doesn't apply to my tree :(".but it can be apply to
> least linux-next branch .
> I make n new patch and send it.I receive
> review(https://www.mail-archive.com/linux-kernel at vger.kernel.org/msg1048115.html)
> .
> I want to know what's wrong with me?
> how do I know that my patch is accepted?
>
Greg said your patch doesn't apply to his staging-next branch (located
in the following repo):
https://git.kernel.org/cgit/linux/kernel/git/gregkh/staging.git/
If you look at the comedi.h file on the HEAD of that branch with git
blame you will see the following patch has already been applied that
fixes up the comments:
f904c4 | 2015-11-12 | Staging: comedi: Fixed multiple commenting and spacing codig style issues. (Daniel H. Hemmingsen)
snits
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2015-12-27 22:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 3:37 first patch maoma king
2015-12-23 4:02 ` Mike Krinkin
2015-12-27 22:28 ` Jerry Snitselaar [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-08-02 21:49 First patch Arkadiusz Lis
2018-08-03 6:36 ` valdis.kletnieks at vt.edu
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=20151227222810.GA24677@rhwork.redhat.com \
--to=dev@snitselaar.org \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).