From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: maoma king <albert008.xu@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, Ian Abbott <abbotti@mev.co.uk>,
Colin Cronin <colinpatrickcronin@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: comedi: fix block comments coding style issue in comedi.h
Date: Wed, 23 Dec 2015 09:55:28 +0530 [thread overview]
Message-ID: <20151223042527.GA3644@sudip-pc> (raw)
In-Reply-To: <CAKNa9uA+=cxhybFTH4rk-R=w7xQYc5R5F7=xgr0nV74dERDYnw@mail.gmail.com>
On Wed, Dec 23, 2015 at 10:51:11AM +0800, maoma king wrote:
> Dear Greg
> 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@vger.kernel.org/msg1048115.html)
> .
> I want to know what's wrong with me?
Nothing is wrong with me. Just work with staging-testing branch of
staging tree and everything should be fine. Ofcourse, if some one else
sends another patch before you touching the same code that you have
worked on then your patch may not apply. But that is part of the game.
> how do I know that my patch is accepted?
When Greg applies any patch to his tree, one confirmation mail will be
automatically sent.
regards
sudip
next prev parent reply other threads:[~2015-12-23 4:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 7:41 [PATCH] Staging: comedi: fix block comments coding style issue in comedi.h maomao xu
2015-12-22 0:02 ` Greg KH
2015-12-23 2:51 ` maoma king
2015-12-23 4:25 ` Sudip Mukherjee [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-22 5:41 maomao xu
2015-12-22 9:13 ` Ian Abbott
2015-11-18 10:09 maomao xu
[not found] <1447075224-7621-1-git-send-email-albert008.xu@yahoo.com>
2015-11-09 14:48 ` Greg KH
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=20151223042527.GA3644@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=abbotti@mev.co.uk \
--cc=albert008.xu@gmail.com \
--cc=colinpatrickcronin@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--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