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
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
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
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
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
Friday, March 14, 2014, 2:29:43 AM, you wrote:
Hi Sander,
On 03/13/2014 08:49 PM, Sander Eikelenboom wrote:
sarcasm on
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)
sarcasm off
(it
On Sat, Mar 15, 2014 at 6:51 AM, Sander Eikelenboom
li...@eikelenboom.it 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),
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
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 merely
On Sat, Mar 15, 2014 at 1:45 PM, Peter Hurley pe...@hurleysoftware.com 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
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
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
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
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 from last week
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 exactly 0
(zero) response.
Hi Sander,
On 03/13/2014 08:49 PM, Sander Eikelenboom wrote:
sarcasm on
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)
sarcasm off
(it was not in John's nor Dave's last pull request, although
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
>>
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) response.
18 matches
Mail list logo
