From: Dan Carpenter <dan.carpenter@oracle.com>
To: DaeSeok Youn <daeseok.youn@gmail.com>
Cc: Lidza Louina <lidza.louina@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>,
devel <devel@driverdev.osuosl.org>,
driverdev-devel@linuxdriverproject.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/6 RESEND] staging: dgap: remove useless dgap_probe1() function
Date: Mon, 2 Jun 2014 13:13:27 +0300 [thread overview]
Message-ID: <20140602101327.GU17724@mwanda> (raw)
In-Reply-To: <CAHb8M2BE+Nn0L3o1nWFbg0XCor8CUDB+1YxdzHAxfWXhFnLHYQ@mail.gmail.com>
On Mon, Jun 02, 2014 at 06:35:15PM +0900, DaeSeok Youn wrote:
> Hi, Dan.
>
> 2014-06-02 16:30 GMT+09:00 Dan Carpenter <dan.carpenter@oracle.com>:
> > On Mon, Jun 02, 2014 at 02:03:58PM +0900, Daeseok Youn wrote:
> >> The dgap_probe1() function is just calling dgap_found_board().
> >> So it is removed and dgap_found_board() is called directly.
> >>
> >> Signed-off-by: Daeseok Youn <daeseok.youn@gmail.com>
> >> ---
> >> RESEND : this patch is included into newly serise of patches
> >> so renumbered and resend.
> >
> > Don't do this. Just assume that patch will be applied. Greg applies
> > patches in first come, first serve order. If it doesn't apply then he
> > sends an email to redo it.
> Ok. I will not do like this again. sorry,
> I should wait for merge first two patches or send my patches
> without the first two patches.
Don't bother waiting. Just send the next patches. The first ones were
good patches, so Greg will apply them. It is a very predictable
process.
regards,
dan carpenter
next prev parent reply other threads:[~2014-06-02 10:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 5:03 [PATCH 1/6 RESEND] staging: dgap: remove useless dgap_probe1() function Daeseok Youn
2014-06-02 7:30 ` Dan Carpenter
2014-06-02 9:35 ` DaeSeok Youn
2014-06-02 10:13 ` Dan Carpenter [this message]
2014-06-02 22:59 ` DaeSeok Youn
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=20140602101327.GU17724@mwanda \
--to=dan.carpenter@oracle.com \
--cc=daeseok.youn@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=lidza.louina@gmail.com \
--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