On Mon, 2012-07-23 at 14:38 +0100, Mel Gorman wrote:
> Changelog since V1
> o Expand some of the notes (jrnieder)
> o Correct upstream commit SHA1 (hugh)
>
> This series is related to the new addition to stable_kernel_rules.txt
>
On Mon, 2012-07-23 at 14:38 +0100, Mel Gorman wrote:
Changelog since V1
o Expand some of the notes (jrnieder)
o Correct upstream commit SHA1 (hugh)
This series is related to the new addition to stable_kernel_rules.txt
-
On Wed, Jul 25, 2012 at 03:30:57PM -0700, Greg KH wrote:
> >
> > All of the patches will apply to 3.0-stable but the ordering of the
> > patches is such that applying them to 3.2-stable and 3.4-stable should
> > be straight-forward.
>
> I can't find any of these that should have gone to
On Mon, Jul 23, 2012 at 02:38:13PM +0100, Mel Gorman wrote:
> Changelog since V1
> o Expand some of the notes (jrnieder)
> o Correct upstream commit SHA1 (hugh)
>
> This series is related to the new addition to
On Mon, Jul 23, 2012 at 02:38:13PM +0100, Mel Gorman wrote:
Changelog since V1
o Expand some of the notes (jrnieder)
o Correct upstream commit SHA1 (hugh)
This series is related to the new addition to stable_kernel_rules.txt
On Wed, Jul 25, 2012 at 03:30:57PM -0700, Greg KH wrote:
SNIP
All of the patches will apply to 3.0-stable but the ordering of the
patches is such that applying them to 3.2-stable and 3.4-stable should
be straight-forward.
I can't find any of these that should have gone to 3.4-stable,
On Tue, 2012-07-24 at 22:18 +0800, Hillf Danton wrote:
> On Tue, Jul 24, 2012 at 9:52 PM, Mike Galbraith wrote:
> > Last time I looked, handling SUSE support issues on LKML was not in my
> > job description. I don't recall seeing anything about taking direction
> > from random LKML subscribers
On Tue, Jul 24, 2012 at 9:52 PM, Mike Galbraith wrote:
> Last time I looked, handling SUSE support issues on LKML was not in my
> job description. I don't recall seeing anything about taking direction
> from random LKML subscribers either.
>
End users pay for SUSE products/service, right?
--
To
On Tue, Jul 24, 2012 at 9:53 PM, Mel Gorman wrote:
> On Tue, Jul 24, 2012 at 09:34:56PM +0800, Hillf Danton wrote:
>> On Tue, Jul 24, 2012 at 9:27 PM, Mel Gorman wrote:
>> > I would suggest the user in question use the normal support channels for
>> > resolving a potentially SLES-specific bug.
On Tue, Jul 24, 2012 at 09:34:56PM +0800, Hillf Danton wrote:
> On Tue, Jul 24, 2012 at 9:27 PM, Mel Gorman wrote:
> > I would suggest the user in question use the normal support channels for
> > resolving a potentially SLES-specific bug.
> >
> Thanks, Mel.
>
> Is Mike busy in other fairs?
It's
On Tue, 2012-07-24 at 21:18 +0800, Hillf Danton wrote:
> On Tue, Jul 24, 2012 at 1:58 PM, Mike Galbraith wrote:
> > FWIW, I'm all for performance backports. They do have a downside though
> > (other than the risk of bugs slipping in, or triggering latent bugs).
> >
> > When the next enterprise
On Tue, Jul 24, 2012 at 9:27 PM, Mel Gorman wrote:
> I would suggest the user in question use the normal support channels for
> resolving a potentially SLES-specific bug.
>
Thanks, Mel.
Is Mike busy in other fairs?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On Tue, Jul 24, 2012 at 09:18:16PM +0800, Hillf Danton wrote:
> On Tue, Jul 24, 2012 at 1:58 PM, Mike Galbraith wrote:
> > FWIW, I'm all for performance backports. They do have a downside though
> > (other than the risk of bugs slipping in, or triggering latent bugs).
> >
> > When the next
On Tue, Jul 24, 2012 at 1:58 PM, Mike Galbraith wrote:
> FWIW, I'm all for performance backports. They do have a downside though
> (other than the risk of bugs slipping in, or triggering latent bugs).
>
> When the next enterprise kernel is built, marketeers ask for numbers to
> make potential
On Tue, Jul 24, 2012 at 07:58:51AM +0200, Mike Galbraith wrote:
> On Mon, 2012-07-23 at 14:38 +0100, Mel Gorman wrote:
> > Changelog since V1
> > o Expand some of the notes
> > (jrnieder)
> > o Correct upstream commit SHA1
On Tue, Jul 24, 2012 at 07:58:51AM +0200, Mike Galbraith wrote:
On Mon, 2012-07-23 at 14:38 +0100, Mel Gorman wrote:
Changelog since V1
o Expand some of the notes
(jrnieder)
o Correct upstream commit SHA1(hugh)
On Tue, Jul 24, 2012 at 1:58 PM, Mike Galbraith efa...@gmx.de wrote:
FWIW, I'm all for performance backports. They do have a downside though
(other than the risk of bugs slipping in, or triggering latent bugs).
When the next enterprise kernel is built, marketeers ask for numbers to
make
On Tue, Jul 24, 2012 at 09:18:16PM +0800, Hillf Danton wrote:
On Tue, Jul 24, 2012 at 1:58 PM, Mike Galbraith efa...@gmx.de wrote:
FWIW, I'm all for performance backports. They do have a downside though
(other than the risk of bugs slipping in, or triggering latent bugs).
When the next
On Tue, Jul 24, 2012 at 9:27 PM, Mel Gorman mgor...@suse.de wrote:
I would suggest the user in question use the normal support channels for
resolving a potentially SLES-specific bug.
Thanks, Mel.
Is Mike busy in other fairs?
--
To unsubscribe from this list: send the line unsubscribe
On Tue, 2012-07-24 at 21:18 +0800, Hillf Danton wrote:
On Tue, Jul 24, 2012 at 1:58 PM, Mike Galbraith efa...@gmx.de wrote:
FWIW, I'm all for performance backports. They do have a downside though
(other than the risk of bugs slipping in, or triggering latent bugs).
When the next
On Tue, Jul 24, 2012 at 09:34:56PM +0800, Hillf Danton wrote:
On Tue, Jul 24, 2012 at 9:27 PM, Mel Gorman mgor...@suse.de wrote:
I would suggest the user in question use the normal support channels for
resolving a potentially SLES-specific bug.
Thanks, Mel.
Is Mike busy in other fairs?
On Tue, Jul 24, 2012 at 9:53 PM, Mel Gorman mgor...@suse.de wrote:
On Tue, Jul 24, 2012 at 09:34:56PM +0800, Hillf Danton wrote:
On Tue, Jul 24, 2012 at 9:27 PM, Mel Gorman mgor...@suse.de wrote:
I would suggest the user in question use the normal support channels for
resolving a potentially
On Tue, Jul 24, 2012 at 9:52 PM, Mike Galbraith efa...@gmx.de wrote:
Last time I looked, handling SUSE support issues on LKML was not in my
job description. I don't recall seeing anything about taking direction
from random LKML subscribers either.
End users pay for SUSE products/service,
On Tue, 2012-07-24 at 22:18 +0800, Hillf Danton wrote:
On Tue, Jul 24, 2012 at 9:52 PM, Mike Galbraith efa...@gmx.de wrote:
Last time I looked, handling SUSE support issues on LKML was not in my
job description. I don't recall seeing anything about taking direction
from random LKML
On Mon, 2012-07-23 at 14:38 +0100, Mel Gorman wrote:
> Changelog since V1
> o Expand some of the notes (jrnieder)
> o Correct upstream commit SHA1 (hugh)
>
> This series is related to the new addition to stable_kernel_rules.txt
>
Changelog since V1
o Expand some of the notes(jrnieder)
o Correct upstream commit SHA1(hugh)
This series is related to the new addition to stable_kernel_rules.txt
- Serious issues as reported by a user of a distribution
On Sun, Jul 22, 2012 at 11:58:32PM +0100, Ben Hutchings wrote:
> I'm about to put 3.2.24 out for review, and it's pretty big already so
> I'm going to defer these to 3.2.25. I haven't forgotten or rejected
> them.
>
No worries, thanks for considering them. I still have to resend the series
with
On Sun, Jul 22, 2012 at 11:58:32PM +0100, Ben Hutchings wrote:
I'm about to put 3.2.24 out for review, and it's pretty big already so
I'm going to defer these to 3.2.25. I haven't forgotten or rejected
them.
No worries, thanks for considering them. I still have to resend the series
with
Changelog since V1
o Expand some of the notes(jrnieder)
o Correct upstream commit SHA1(hugh)
This series is related to the new addition to stable_kernel_rules.txt
- Serious issues as reported by a user of a distribution
On Mon, 2012-07-23 at 14:38 +0100, Mel Gorman wrote:
Changelog since V1
o Expand some of the notes (jrnieder)
o Correct upstream commit SHA1 (hugh)
This series is related to the new addition to stable_kernel_rules.txt
-
I'm about to put 3.2.24 out for review, and it's pretty big already so
I'm going to defer these to 3.2.25. I haven't forgotten or rejected
them.
Ben.
--
Ben Hutchings
73.46% of all statistics are made up.
signature.asc
Description: This is a digitally signed message part
I'm about to put 3.2.24 out for review, and it's pretty big already so
I'm going to defer these to 3.2.25. I haven't forgotten or rejected
them.
Ben.
--
Ben Hutchings
73.46% of all statistics are made up.
signature.asc
Description: This is a digitally signed message part
This series is related to the new addition to stable_kernel_rules.txt
- Serious issues as reported by a user of a distribution kernel may also
be considered if they fix a notable performance or interactivity issue.
As these fixes are not as obvious and have a higher risk of a subtle
This series is related to the new addition to stable_kernel_rules.txt
- Serious issues as reported by a user of a distribution kernel may also
be considered if they fix a notable performance or interactivity issue.
As these fixes are not as obvious and have a higher risk of a subtle
34 matches
Mail list logo
