linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>,
	Kalle Valo <kvalo@adurom.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	<linux-wireless@vger.kernel.org>, Jason Baron <jbaron@redhat.com>
Subject: Re: [RFC] How to manage dependency between patches
Date: Sun, 2 Dec 2012 10:14:07 +0200	[thread overview]
Message-ID: <4690706.ontQQdo20b@lx-vladimir> (raw)
In-Reply-To: <20121201023800.GD2355@tuxdriver.com>

On Friday, November 30, 2012 09:38:00 PM John W. Linville wrote:
> Since Greg is merging one patch and I'm merging the other, under
> normal circumstances they will only reach the same tree sometime
> during the 3.8 merge window.  FWIW, I was under the impression that
> you were targeting 3.9 anyway.  If so, you can simply wait to have
> your driver merged sometime after 3.8-rc1.
> 
> Does that help?
> 
> John
> 

Thanks John,

Actually, I was after 3.8; but I understand in my situation it may be
not feasible.

Positive side is till 3.9 I can integrate more features;
negative one is... the same - since I will end up with one bulky patch.

I'd actually prefer to have baseline merged, and then submit 'feature'
patches - it will be easier to review.

By the way - what is better, hold new features till initial driver merged,
or keep integrating more and more stuff?

Thanks, Vladimir



  reply	other threads:[~2012-12-02  8:14 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-15 11:16 [PATCH v8 0/4] driver for 60g Wilocity chip wil6210 Vladimir Kondratiev
2012-11-15 11:16 ` [PATCH v8 1/4] wireless: Driver for 60GHz card wil6210 Vladimir Kondratiev
2012-11-15 11:17 ` [PATCH v8 2/4] wireless: allow Atheros card to not depend on ath.ko Vladimir Kondratiev
2012-11-21 11:18   ` Vladimir Kondratiev
2012-11-21 14:55     ` Kalle Valo
     [not found]       ` <CAB=NE6XP83QVZ8Vv1R247HLW3ep_quQ8yP9STKT5L_jMrpxUOA@mail.gmail.com>
2012-11-22  7:08         ` Kalle Valo
     [not found]           ` <CAB=NE6V2DTQD9Q2Chj0ftk4oYE1aykCJtCaeAu_WSp3RTVSjhA@mail.gmail.com>
2012-11-26 17:54             ` Vladimir Kondratiev
2012-11-28 13:55               ` Vladimir Kondratiev
2012-11-28 14:13                 ` John W. Linville
2012-11-28 15:51                   ` Vladimir Kondratiev
2012-11-28 15:53                   ` [PATCH v2] " Vladimir Kondratiev
2012-11-28 16:59                     ` Vladimir Kondratiev
     [not found]                     ` <1585902.GCBvcuyASu@lx-vladimir>
2012-12-01  2:38                       ` [RFC] How to manage dependency between patches John W. Linville
2012-12-02  8:14                         ` Vladimir Kondratiev [this message]
2012-11-28 16:57                   ` [PATCH v2] wireless: allow Atheros card to not depend on ath.ko Vladimir Kondratiev
2012-12-03 13:03                     ` Vladimir Kondratiev
2012-12-03 13:46                       ` John W. Linville
2012-12-04  7:59                         ` Vladimir Kondratiev
2012-12-11 19:28                     ` Kalle Valo
2012-12-12  8:07                       ` Vladimir Kondratiev
2012-12-12  8:58                       ` [PATCH] wireless: fix Atheros drivers compilation Vladimir Kondratiev
2012-12-12 17:08                         ` Kalle Valo
2012-12-12 17:25                           ` [PATCH v2] " Vladimir Kondratiev
2012-12-12 17:32                             ` Kalle Valo
2012-11-15 11:17 ` [PATCH v8 3/4] wireless: integrate wil6210 driver into build Vladimir Kondratiev
2012-11-15 11:17 ` [PATCH v8 4/4] dynamic_debug: dynamic hex dump Vladimir Kondratiev
2012-11-15 11:52   ` Vladimir Kondratiev
2012-11-15 15:55   ` Andrei Emeltchenko
2012-11-15 17:32     ` Joe Perches

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=4690706.ontQQdo20b@lx-vladimir \
    --to=qca_vkondrat@qca.qualcomm.com \
    --cc=jbaron@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=kvalo@adurom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rodrigue@qca.qualcomm.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;
as well as URLs for NNTP newsgroup(s).