From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Nikolay Martynov <mar.kolya@gmail.com>,
"mar.kolya@gmail.com linux-wireless@vger.kernel.org"
<linux-wireless@vger.kernel.org>,
"ilw@linux.intel.com" <ilw@linux.intel.com>
Subject: Re: [PATCH] iwlwifi regression in 20111205 merge
Date: Fri, 09 Dec 2011 09:00:35 -0800 [thread overview]
Message-ID: <1323450035.13074.154.camel@wwguy-huron> (raw)
In-Reply-To: <20111209165138.GB14236@tuxdriver.com>
On Fri, 2011-12-09 at 08:51 -0800, John W. Linville wrote:
> On Fri, Dec 09, 2011 at 07:15:27AM -0800, Guy, Wey-Yi wrote:
> > On Fri, 2011-12-09 at 07:44 -0800, John W. Linville wrote:
> > > Are the bits in the wireless tree correct? If so, then please just
> > > send a patch to fix the wireless-next tree.
> > >
> > > Now that the kernel.org mess is sorted, I guess we/I need to go back
> > > to pulling your trees instead of applying patches...
> > >
> > "wireless" tree is correct, the piece is missing in iwl-mac80211.c on
> > "wireless-next" tree. Nikolay's patch fix it.
> >
> > The question I have is what is the right way to deal with this. the
> > orig. patch need to be backport to stable, but the function was move to
> > different file short before the patch. That is the reason cause this
> > mess :-)
>
> Once it has made it to Linus, you can send a patch for
> stable@vger.kernel.org referencing the commit ID in Linus' tree.
>
> If you mean that the change needs to go to wireless but the function
> has moved in wireless-next, then post the patch for wireless. Usually
> I can figure-out the merge (although apparently not in this case).
> If you think the merge will be tricky, you can send a reference patch
> for wireless-next for me to use as a guide when fixing-up the merge.
> Or you can pull your fixes tree into your -next tree, resolve the
> merge conflict, and ask me to pull. Or you can wait until the merge
> breakage happens, and send a patch. :-)
>
Thank you for the advise and I will try my best to make sure not happen
again :-)
Thanks
Wey
prev parent reply other threads:[~2011-12-09 17:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 2:43 [PATCH] iwlwifi regression in 20111205 merge Nikolay Martynov
2011-12-09 3:03 ` Guy, Wey-Yi
2011-12-09 3:15 ` Guy, Wey-Yi
2011-12-09 15:44 ` John W. Linville
2011-12-09 15:15 ` Guy, Wey-Yi
2011-12-09 16:51 ` John W. Linville
2011-12-09 17:00 ` Guy, Wey-Yi [this message]
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=1323450035.13074.154.camel@wwguy-huron \
--to=wey-yi.w.guy@intel.com \
--cc=ilw@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mar.kolya@gmail.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.