From: David Miller <davem@davemloft.net>
To: petkan@nucleusys.com
Cc: romieu@fr.zoreil.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] drivers: net: usb: rtl8150: bug fixing and cleanup
Date: Mon, 20 May 2013 00:00:46 -0700 (PDT) [thread overview]
Message-ID: <20130520.000046.631828458050532836.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1305200941260.4719@fry.nucleusys.com>
From: Petko Manolov <petkan@nucleusys.com>
Date: Mon, 20 May 2013 09:58:39 +0300 (EEST)
> So first apply patch #1 and then patch #2.
Then nobody can properly GIT bisect through your patch series.
The tree must work and build properly at each and every step
of your patch series.
next prev parent reply other threads:[~2013-05-20 7:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-18 16:23 Petko Manolov
2013-05-18 21:09 ` Francois Romieu
2013-05-19 8:42 ` Petko Manolov
2013-05-19 19:01 ` Francois Romieu
2013-05-20 6:58 ` Petko Manolov
2013-05-20 7:00 ` David Miller [this message]
2013-05-20 7:09 ` Petko Manolov
2013-05-20 7:12 ` David Miller
2013-05-20 7:18 ` Petko Manolov
2013-05-20 7:43 ` David Miller
2013-05-20 7:49 ` Petko Manolov
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=20130520.000046.631828458050532836.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=petkan@nucleusys.com \
--cc=romieu@fr.zoreil.com \
/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
all inboxes | Powered by JetHome®