On Sat, Mar 15, 2014 at 1:45 PM, Peter Hurley wrote:
>
> FWIW, the 'known breakage' for 3.14 is a (valid) lockdep report.
Ok, if it's just lockdep and unlikely to hit in real life and getting
fixed later, I guess I don't really care all that deeply for 3.14
Linus
--
To unsubscr
Saturday, March 15, 2014, 9:45:03 PM, you wrote:
> On 03/15/2014 01:53 PM, Linus Torvalds wrote:
>> Guys, why is this being discussed?
> FWIW, the 'known breakage' for 3.14 is a (valid) lockdep report.
Hmm .. whoops you are right .. i remembered it as being an "oops",
but you are right it was m
On 03/15/2014 01:53 PM, Linus Torvalds wrote:
Guys, why is this being discussed?
FWIW, the 'known breakage' for 3.14 is a (valid) lockdep report.
This regression was introduced by a small patchset added to -next
over the holidays that was intended to address 2 bug reports
stemming from a long-
On Sat, Mar 15, 2014 at 6:51 AM, Sander Eikelenboom
wrote:
>
>
> Ok but the breakage/regression was known since around the merge window.
> I thought the "standard policy" when things cause new regression and are not
> fixable (too intrusive, too time consuming you
> name the reason), was to rever
Friday, March 14, 2014, 2:29:43 AM, you wrote:
> Hi Sander,
> On 03/13/2014 08:49 PM, Sander Eikelenboom wrote:
>>
>> Is it just me .. or is this going at the speed of about a bluetooth
>> connection ..
>> and probably missing the boot for 3.14 ? (for no good reason IMHO)
>>
>>
>> (it was not
Hi Sander,
On 03/13/2014 08:49 PM, Sander Eikelenboom wrote:
Is it just me .. or is this going at the speed of about a bluetooth connection
..
and probably missing the boot for 3.14 ? (for no good reason IMHO)
(it was not in John's nor Dave's last pull request, although it seems to be
rever
Hi Sander,
Since:
- 3.14-RC6 has been cut
- this regression is known and reported since the merge window
- the fix (revert of 3 patches) is known for over a month now
- but it's still not in mainline
- my polite ping request from last week seems to have provoked exact
Tuesday, March 11, 2014, 4:14:38 PM, you wrote:
> Hi John,
>>> Since:
>>> - 3.14-RC6 has been cut
>>> - this regression is known and reported since the merge window
>>> - the fix (revert of 3 patches) is known for over a month now
>>> - but it's still not in mainline
>>> - my polite ping request
Hi John,
>> Since:
>> - 3.14-RC6 has been cut
>> - this regression is known and reported since the merge window
>> - the fix (revert of 3 patches) is known for over a month now
>> - but it's still not in mainline
>> - my polite ping request from last week seems to have provoked exactly 0
>> (zero
On Mon, Mar 10, 2014 at 09:38:43AM +0100, Sander Eikelenboom wrote:
> Hi all,
>
> Since:
> - 3.14-RC6 has been cut
> - this regression is known and reported since the merge window
> - the fix (revert of 3 patches) is known for over a month now
> - but it's still not in mainline
> - my polite ping
Hi all,
Since:
- 3.14-RC6 has been cut
- this regression is known and reported since the merge window
- the fix (revert of 3 patches) is known for over a month now
- but it's still not in mainline
- my polite ping request from last week seems to have provoked exactly 0 (zero)
response.
IT'S TIME
Wednesday, February 12, 2014, 12:06:44 PM, you wrote:
> Monday, February 10, 2014, 11:09:38 PM, you wrote:
>> Hi Peter,
>>> This patch series addresses a number of previously unknown issues
>>> with the RFCOMM tty device implementation, in addition to
>>> addressing the locking regression recen
Hi Peter,
> This patch series addresses a number of previously unknown issues
> with the RFCOMM tty device implementation, in addition to
> addressing the locking regression recently reported [1].
>
> As Gianluca suggested and I agree, this series first reverts
> 3 of the 4 patches of 3.14-rc1 fo
Am 13.02.2014 01:38, schrieb Peter Hurley:
Hi Marcel,
On 02/12/2014 05:58 PM, Marcel Holtmann wrote:
we might also want to add some end-to-end test cases to rfcomm-tester
that covers this behavior.
Sounds great. Such would have found the problem with disappearing remote
bt (rfcomm) devices s
Am 10.02.2014 02:59, schrieb Peter Hurley:
Marcel,
This patch series addresses a number of previously unknown issues
with the RFCOMM tty device implementation, in addition to
addressing the locking regression recently reported [1].
As Gianluca suggested and I agree, this series first reverts
3
Hi Marcel,
On 02/12/2014 05:58 PM, Marcel Holtmann wrote:
we might also want to add some end-to-end test cases to rfcomm-tester that
covers this behavior.
Are there some docs for the linux-bluetooth test harness?
I have some unit tests that I can port but I should probably understand
the blu
Hi Peter,
>>> This patch series addresses a number of previously unknown issues
>>> with the RFCOMM tty device implementation, in addition to
>>> addressing the locking regression recently reported [1].
>>>
>>> As Gianluca suggested and I agree, this series first reverts
>>> 3 of the 4 patches of
Monday, February 10, 2014, 11:09:38 PM, you wrote:
> Hi Peter,
>> This patch series addresses a number of previously unknown issues
>> with the RFCOMM tty device implementation, in addition to
>> addressing the locking regression recently reported [1].
>>
>> As Gianluca suggested and I agree, t
Hi Marcel,
On 02/10/2014 05:09 PM, Marcel Holtmann wrote:
Hi Peter,
This patch series addresses a number of previously unknown issues
with the RFCOMM tty device implementation, in addition to
addressing the locking regression recently reported [1].
As Gianluca suggested and I agree, this seri
Hi Peter,
> This patch series addresses a number of previously unknown issues
> with the RFCOMM tty device implementation, in addition to
> addressing the locking regression recently reported [1].
>
> As Gianluca suggested and I agree, this series first reverts
> 3 of the 4 patches of 3.14-rc1 fo
Marcel,
This patch series addresses a number of previously unknown issues
with the RFCOMM tty device implementation, in addition to
addressing the locking regression recently reported [1].
As Gianluca suggested and I agree, this series first reverts
3 of the 4 patches of 3.14-rc1 for bluetooth/rf
21 matches
Mail list logo
