From: "John W. Linville" <linville@tuxdriver.com>
To: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.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: Fri, 30 Nov 2012 21:38:00 -0500 [thread overview]
Message-ID: <20121201023800.GD2355@tuxdriver.com> (raw)
In-Reply-To: <1585902.GCBvcuyASu@lx-vladimir>
On Thu, Nov 29, 2012 at 11:29:55AM +0200, Vladimir Kondratiev wrote:
> Hi,
>
> I have the following situation:
>
> - there is the driver for 60g WiFi card, "wil6210", that I want to merge. It
> consists of 2 patches:
>
> wireless: Driver for 60GHz card wil6210
> wireless: integrate wil6210 driver into build
>
> - then, there is one more patch for Atheros drivers family config that I rely
> on:
>
> wireless: allow Atheros card to not depend on ath.ko
>
> - and, there is one more patch that I depend on:
>
> dynamic_debug: dynamic hex dump
>
> Discussion about last patch was taken from linux-wireless to the LKML, and it
> get pushed to Greg K-H by Jason Baron.
>
> So, question is: what is the right strategy for wil6210 driver?
>
> Shall I wait till 2 patches I depend on get merged? Some other idea?
>
> Please advise.
>
> Thanks, Vladimir
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
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2012-12-01 2:46 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 ` John W. Linville [this message]
2012-12-02 8:14 ` [RFC] How to manage dependency between patches Vladimir Kondratiev
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=20121201023800.GD2355@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=jbaron@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@adurom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=qca_vkondrat@qca.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.