Hi Everyone,
Unfortunately we were forced to rebase the bluetooth-next tree on top of the
wireless-next tree of today (commit 341352d), we apologize for the problems
this may cause to you.
And there is more, I also had to edit some commits to fix coding style issues.
So don't worry if some piece of the code looks slightly different from what
you wrote, it was just style fix.
Our apologizes!
Gustavo
Hi Mat,
* Mat Martineau <[email protected]> [2012-05-09 10:52:47 -0700]:
>
> Gustavo -
>
> On Wed, 9 May 2012, Gustavo Padovan wrote:
>
> >Hi Everyone,
> >
> >Unfortunately we were forced to rebase the bluetooth-next tree on top of the
> >wireless-next tree of today (commit 341352d), we apologize for the problems
> >this may cause to you.
> >
> >And there is more, I also had to edit some commits to fix coding style issues.
> >So don't worry if some piece of the code looks slightly different from what
> >you wrote, it was just style fix.
> >
> >Our apologizes!
>
> Any plans for merging bluetooth in to bluetooth-next? I assume
> you're waiting for John to pull the bluetooth branch.
Exactly, this should happen soon.
Gustavo
Gustavo -
On Wed, 9 May 2012, Gustavo Padovan wrote:
> Hi Everyone,
>
> Unfortunately we were forced to rebase the bluetooth-next tree on top of the
> wireless-next tree of today (commit 341352d), we apologize for the problems
> this may cause to you.
>
> And there is more, I also had to edit some commits to fix coding style issues.
> So don't worry if some piece of the code looks slightly different from what
> you wrote, it was just style fix.
>
> Our apologizes!
Any plans for merging bluetooth in to bluetooth-next? I assume you're
waiting for John to pull the bluetooth branch.
I have an upcoming patch set for bluetooth-next that depends on
patches in the bluetooth branch.
--
Mat Martineau
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum