On Fri, Jul 12, 2013 at 1:04 AM, Aaro Koskinen aaro.koski...@iki.fi wrote:
Commit 42913c799 (MIPS: Loongson2: Use clk API instead of direct
dereferences) broke the cpufreq functionality on Loongson2 boards:
clk_set_rate() is called before the CPU frequency table is initialized,
and therefore
On Thu, 2013-07-11 at 20:34 -0700, Greg Kroah-Hartman wrote:
On Thu, Jul 11, 2013 at 10:57:46PM -0400, John W. Linville wrote:
On Thu, Jul 11, 2013 at 08:50:23PM -0400, Theodore Ts'o wrote:
In any case, I've been very conservative in _not_ pushing bug fixes to
Linus after -rc3 (unless
On Mon, Jul 08, 2013 at 03:20:26PM +0100, Jan Beulich wrote:
On 08.07.13 at 11:59, Jan Beulich jbeul...@suse.com wrote:
On 05.07.13 at 16:53, Wei Liu wei.l...@citrix.com wrote:
On Fri, Jul 05, 2013 at 10:32:41AM +0100, Jan Beulich wrote:
--- a/drivers/net/xen-netfront.c
+++
On 12.07.13 at 10:32, Wei Liu wei.l...@citrix.com wrote:
On Mon, Jul 08, 2013 at 03:20:26PM +0100, Jan Beulich wrote:
On 08.07.13 at 11:59, Jan Beulich jbeul...@suse.com wrote:
On 05.07.13 at 16:53, Wei Liu wei.l...@citrix.com wrote:
skb-truesize += PAGE_SIZE * skb_shinfo(skb)-nr_frags;
On Thu, 11 Jul 2013, Steven Rostedt wrote:
Maybe the pendulum has swung too far in the direction of holding back
changes and trying to avoid the risk of introducing regressions;
perhaps this would be a good topic to discuss at the Kernel Summit.
Bah, I sent out a similar email about
On Fri, Jul 12, 2013 at 5:46 AM, Jiri Kosina jkos...@suse.cz wrote:
On Thu, 11 Jul 2013, Steven Rostedt wrote:
Maybe the pendulum has swung too far in the direction of holding back
changes and trying to avoid the risk of introducing regressions;
perhaps this would be a good topic to
On 7/12/2013 3:06 AM, Greg KH wrote:
On Fri, Jul 12, 2013 at 03:00:14AM +0200, Rafael J. Wysocki wrote:
On 7/12/2013 2:53 AM, Rafael J. Wysocki wrote:
On 7/12/2013 2:37 AM, Greg KH wrote:
On Fri, Jul 12, 2013 at 02:32:07AM +0200, Rafael J. Wysocki wrote:
On 7/12/2013 2:29 AM, Greg KH wrote:
On 7/12/2013 3:05 AM, Greg KH wrote:
On Fri, Jul 12, 2013 at 02:53:37AM +0200, Rafael J. Wysocki wrote:
On 7/12/2013 2:37 AM, Greg KH wrote:
On Fri, Jul 12, 2013 at 02:32:07AM +0200, Rafael J. Wysocki wrote:
On 7/12/2013 2:29 AM, Greg KH wrote:
On Fri, Jul 12, 2013 at 02:22:23AM +0200,
On Tue, Jul 9, 2013 at 10:38 AM, Theodore Ts'o ty...@mit.edu wrote:
On Tue, Jul 09, 2013 at 09:14:29AM -0500, Eric Sandeen wrote:
I don't think these did get cc'd to stable. Was there a reason for that,
or was it an oversight?
It was an oversight; my fault, sorry. I'll send a request to
As we hot-add 128 MB chunks of memory, we wait to ensure that the memory
is onlined before attempting to hot-add the next chunk. If the udev rule for
memory hot-add is not executed within the allowed time, we would rollback the
state and abort further hot-add. Since the hot-add has succeeded and
When we are posting pressure status, we may get interrupted and handle
the un-balloon operation. In this case just don't post the status as we
know the pressure status is stale.
Signed-off-by: K. Y. Srinivasan k...@microsoft.com
Cc: Stable stable@vger.kernel.org
---
drivers/hv/hv_balloon.c |
On Thu, Jul 11, 2013 at 03:20:29PM -0700, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.0.86 release.
There are 8 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
On Thu, Jul 11, 2013 at 03:44:55PM -0700, Greg Kroah-Hartman wrote:
On Thu, Jul 11, 2013 at 06:29:35PM -0400, Dave Jones wrote:
On Thu, Jul 11, 2013 at 03:01:17PM -0700, Greg Kroah-Hartman wrote:
rant
I'm sitting on top of over 170 more patches that have been marked for
the
Hyvää päivää,
Meillä on ilo kirjoittaa teille vielä oikeuta lainoja postitse
ilmoituksesi. Sun East Federal Credit Union, Toimimme lyhyitä,
selkeitä ja ymmärrettäviä ehtoja Annamme lainaa alhaisella korolla
3%. Hyvät lukijat pitäisi huomata, että tämä tarjous on vakava
ajattelevia
From: Christian König christian.koe...@amd.com
Changing the UVD BOs offset on suspend/resume doesn't work because the VCPU
internally keeps pointers to it. Just keep it always pinned and save the
content manually.
Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=66425
v2: fix compiler
From: Alex Deucher alexander.deuc...@amd.com
They still seem to cause instability on some r6xx parts.
As a follow up, we can switch to using CP DMA for bo
moves on r6xx as a lighter weight alternative to using
the 3D engine. Fixes hangs on some cards with heavy
buffer migration.
Tested-by: J.N.
On Fri, Jul 12, 2013 at 09:15:06AM -0400, Josh Boyer wrote:
On Tue, Jul 9, 2013 at 10:38 AM, Theodore Ts'o ty...@mit.edu wrote:
On Tue, Jul 09, 2013 at 09:14:29AM -0500, Eric Sandeen wrote:
I don't think these did get cc'd to stable. Was there a reason for that,
or was it an oversight?
On Thu, Jul 11, 2013 at 03:11:00PM -0700, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.4.53 release.
There are 11 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
On Fri, Jul 12, 2013 at 10:58:46AM -0400, Benjamin LaHaise wrote:
On Thu, Jul 11, 2013 at 03:11:00PM -0700, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.4.53 release.
There are 11 patches in this series, all will be posted as a response
to this one. If
On Fri, Jul 12, 2013 at 7:15 AM, Guenter Roeck li...@roeck-us.net wrote:
I get the impression as soon as we hit -rc1, some maintainers immediately
go into OH SHIT, I CAN'T SEND PATCHES OR LINUS WILL SHOUT AT ME mode.
I agree. But it seems that I need to now start shouting at them :(
On Fri, 2013-07-12 at 08:22 -0700, Linus Torvalds wrote:
Listen to yourself. In fact, there is a damn good solution: don't
mark crap for stable, and don't send crap to me after -rc4.
I tend to hold things off after -rc4 because you scare me more than Greg
does ;-)
Actually, as I consider
On Fri, Jul 12, 2013 at 8:47 AM, Steven Rostedt rost...@goodmis.org wrote:
I tend to hold things off after -rc4 because you scare me more than Greg
does ;-)
Have you guys *seen* Greg? The guy is a freakish giant. He *should*
scare you. He might squish you without ever even noticing.
* Linus Torvalds torva...@linux-foundation.org wrote:
On Fri, Jul 12, 2013 at 8:47 AM, Steven Rostedt rost...@goodmis.org wrote:
I tend to hold things off after -rc4 because you scare me more than Greg
does ;-)
Have you guys *seen* Greg? The guy is a freakish giant. He *should*
scare
On Fri, Jul 12, 2013 at 12:17 PM, Ingo Molnar mi...@kernel.org wrote:
* Linus Torvalds torva...@linux-foundation.org wrote:
On Fri, Jul 12, 2013 at 8:47 AM, Steven Rostedt rost...@goodmis.org wrote:
I tend to hold things off after -rc4 because you scare me more than Greg
does ;-)
Have
On Fri, Jul 12, 2013 at 12:35 PM, Josh Boyer jwbo...@gmail.com wrote:
On Fri, Jul 12, 2013 at 12:17 PM, Ingo Molnar mi...@kernel.org wrote:
* Linus Torvalds torva...@linux-foundation.org wrote:
On Fri, Jul 12, 2013 at 8:47 AM, Steven Rostedt rost...@goodmis.org wrote:
I tend to hold
On Fri, 2013-07-12 at 08:55 -0700, Linus Torvalds wrote:
On Fri, Jul 12, 2013 at 8:47 AM, Steven Rostedt rost...@goodmis.org wrote:
I tend to hold things off after -rc4 because you scare me more than Greg
does ;-)
Have you guys *seen* Greg? The guy is a freakish giant. He *should*
scare
On Fri, Jul 12, 2013 at 12:35:26PM -0400, Josh Boyer wrote:
On Fri, Jul 12, 2013 at 12:17 PM, Ingo Molnar mi...@kernel.org wrote:
* Linus Torvalds torva...@linux-foundation.org wrote:
On Fri, Jul 12, 2013 at 8:47 AM, Steven Rostedt rost...@goodmis.org
wrote:
I tend to hold things
On 07/11/2013 05:50 PM, Theodore Ts'o wrote:
At least at one point in the past...
And at at least one *other* point in the past, Linus stated that
holding back anything with a Cc: stable waiting for the merge window is
wrong. This would imply that the post-rc5-or-so policy and the stable
On 07/11/2013 04:24 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.1 release.
There are 19 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should
On the subject of the stable tree: could we get a standard format for
requesting post-inclusion elevation of patches to stable status? It
isn't all that unusual that the need for -stable is highlighted after a
patch has been included in a maintainer's tree, and rebasing to add
stable metadata
On 07/11/2013 05:19 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.4.53 release.
There are 11 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should
On 07/11/2013 07:24 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.9.10 release.
There are 15 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should
On 07/11/2013 05:44 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.0.86 release.
There are 8 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On Fri, Jul 12, 2013 at 10:20:46AM -0700, H. Peter Anvin wrote:
On the subject of the stable tree: could we get a standard format for
requesting post-inclusion elevation of patches to stable status? It
isn't all that unusual that the need for -stable is highlighted after a
patch has been
On Fri, Jul 12, 2013 at 05:20:29PM +, Shuah Khan wrote:
On 07/11/2013 04:24 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.1 release.
There are 19 patches in this series, all will be posted as a response
to this one. If anyone has any issues
On Fri, Jul 12, 2013 at 06:54:43AM -0700, Guenter Roeck wrote:
On Thu, Jul 11, 2013 at 03:20:29PM -0700, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.0.86 release.
There are 8 patches in this series, all will be posted as a response
to this one. If
On Fri, Jul 12, 2013 at 08:22:27AM -0700, Linus Torvalds wrote:
On Fri, Jul 12, 2013 at 7:15 AM, Guenter Roeck li...@roeck-us.net wrote:
I get the impression as soon as we hit -rc1, some maintainers immediately
go into OH SHIT, I CAN'T SEND PATCHES OR LINUS WILL SHOUT AT ME mode.
I
On Thu, Jul 11, 2013 at 03:11:00PM -0700, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.4.53 release.
There are 11 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
On Fri, Jul 12, 2013 at 10:31 AM, Guenter Roeck li...@roeck-us.net wrote:
Stable rules say: It must fix a real bug that bothers people (not a, This
could be a problem... type thing). All the above fit that rule.
You cut out the important part:
- It must fix a problem that causes a build
On Fri, 2013-07-12 at 10:28 -0700, Greg Kroah-Hartman wrote:
Yes, this requires you to remember to do this after it hits Linus's
tree, so you could do like David does for networking, and keep a
seperate tree to send to me specifically for stable patches. I think he
uses patchwork, but I know
On Fri, Jul 12, 2013 at 10:28:36AM -0700, Greg Kroah-Hartman wrote:
On Fri, Jul 12, 2013 at 10:20:46AM -0700, H. Peter Anvin wrote:
On the subject of the stable tree: could we get a standard format for
requesting post-inclusion elevation of patches to stable status? It
isn't all that
On Fri, Jul 12, 2013 at 10:50 AM, Steven Rostedt rost...@goodmis.org wrote:
Perhaps just make a separate stable branch, where you cherry-pick the
specific patch using the -x option. Adds a (cherry picked from
commit ...). Then you could have some filter that monitors Linus
commits and when a
On Fri, Jul 12, 2013 at 10:50:08AM -0700, Linus Torvalds wrote:
On Fri, Jul 12, 2013 at 10:31 AM, Guenter Roeck li...@roeck-us.net wrote:
Stable rules say: It must fix a real bug that bothers people (not a, This
could be a problem... type thing). All the above fit that rule.
You cut out
On Fri, Jul 12, 2013 at 01:57:18PM -0400, Theodore Ts'o wrote:
On Fri, Jul 12, 2013 at 10:28:36AM -0700, Greg Kroah-Hartman wrote:
On Fri, Jul 12, 2013 at 10:20:46AM -0700, H. Peter Anvin wrote:
On the subject of the stable tree: could we get a standard format for
requesting
On Fri, 2013-07-12 at 10:59 -0700, Linus Torvalds wrote:
On Fri, Jul 12, 2013 at 10:50 AM, Steven Rostedt rost...@goodmis.org wrote:
Perhaps just make a separate stable branch, where you cherry-pick the
specific patch using the -x option. Adds a (cherry picked from
commit ...). Then you
On 07/12/2013 10:57 AM, Theodore Ts'o wrote:
On Fri, Jul 12, 2013 at 10:28:36AM -0700, Greg Kroah-Hartman wrote:
On Fri, Jul 12, 2013 at 10:20:46AM -0700, H. Peter Anvin wrote:
On the subject of the stable tree: could we get a standard format for
requesting post-inclusion elevation of patches
On 07/12/2013 11:16 AM, H. Peter Anvin wrote:
This relates to the a posteori metadata problem with git. In theory I
think git notes should handle those, but I have to admit that git notes
somewhat creep me out because there doesn't seem to be any version
control on them, and as far as I can
On Fri, Jul 12, 2013 at 10:34:56AM -0700, Guenter Roeck wrote:
On Thu, Jul 11, 2013 at 03:11:00PM -0700, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.4.53 release.
There are 11 patches in this series, all will be posted as a response
to this one. If
The unwritten criteria that I've seen used (and sometimes even
discussed on mailing lists) is that if it's something that distro
kernel maintainers would want, then it's fit for stable. Now, there's
a grey area here. The criteria before distro's golden master has
been released is quite different
On Fri, Jul 12, 2013 at 11:28 AM, H. Peter Anvin h...@zytor.com wrote:
OK, just read up some more on git notes, and *both* the assumptions I
had made about git notes were fundamentally wrong. Not sure how well
they would scale, though, but stuffing metadata like additional
Acked-by:,
On Fri, 2013-07-12 at 15:35 -0400, Theodore Ts'o wrote:
So the problem is that maintainers are lazy. They don't want to go
back for bug fixes that have proven themselves, and even if they
aren't critical bug fixes, they are things which a distro maintainer
or a stable kernel user might want
On Fri, Jul 12, 2013 at 10:50:08AM -0700, Linus Torvalds wrote:
So I'm not going to argue that your particular patches were the
problem here. I'm more arguing against your arguments than against the
patches themselves. I'm not looking for some hard black-and-white
rules that say this is
On Fri, 2013-07-12 at 12:44 -0700, Linus Torvalds wrote:
They can be useful for local notes (they can be very powerful for
certain workflows), but they won't be pulled and pushed by me.
Perhaps notes can be used as that reminder to send to stable. Tag a
commit with a note, and have some
On Fri, Jul 12, 2013 at 03:49:11PM -0400, Steven Rostedt wrote:
On Fri, 2013-07-12 at 15:35 -0400, Theodore Ts'o wrote:
So the problem is that maintainers are lazy. They don't want to go
back for bug fixes that have proven themselves, and even if they
aren't critical bug fixes, they are
On Fri, Jul 12, 2013 at 1:53 PM, Steven Rostedt rost...@goodmis.org wrote:
On Fri, 2013-07-12 at 12:44 -0700, Linus Torvalds wrote:
They can be useful for local notes (they can be very powerful for
certain workflows), but they won't be pulled and pushed by me.
Perhaps notes can be used as
On Fri, Jul 12, 2013 at 03:49:11PM -0400, Steven Rostedt wrote:
On Fri, 2013-07-12 at 15:35 -0400, Theodore Ts'o wrote:
So the problem is that maintainers are lazy. They don't want to go
back for bug fixes that have proven themselves, and even if they
aren't critical bug fixes, they
On Fri, Jul 12, 2013 at 06:56:14AM -0700, K. Y. Srinivasan wrote:
As we hot-add 128 MB chunks of memory, we wait to ensure that the memory
is onlined before attempting to hot-add the next chunk. If the udev rule for
memory hot-add is not executed within the allowed time, we would rollback the
On Fri, 2013-07-12 at 16:19 -0400, Dave Jones wrote:
Your example above: If that fix was for tracing reports wrong results, no
big deal,
everyone can live with it for a month. If it was fixing a bug in tracing can
allow
an unprivileged user to crash the kernel, a month is unacceptable, and
On Fri, 2013-07-12 at 16:28 -0400, Steven Rostedt wrote:
On Fri, 2013-07-12 at 16:19 -0400, Dave Jones wrote:
I would suspect that machines that allow unprivileged users would be
running distro kernels, and not the latest release from Linus, and thus
even a bug that can allow an unprivileged
On Fri, Jul 12, 2013 at 03:53:17PM -0400, Steven Rostedt wrote:
On Fri, 2013-07-12 at 12:44 -0700, Linus Torvalds wrote:
They can be useful for local notes (they can be very powerful for
certain workflows), but they won't be pulled and pushed by me.
Perhaps notes can be used as that
On Fri, 2013-07-12 at 13:33 -0700, Greg Kroah-Hartman wrote:
That's what mailboxes are for, use a script of 'git send-email' to send
it to yourself and save it somewhere. Use patchwork. Use a text file
to remind yourself. Use quilt, like Andrew does, he has a great track
record of marking
On Fri, Jul 12, 2013 at 09:50:51PM +0200, Willy Tarreau wrote:
So probably we should incite patch contributors to add a specific
tag such as Fixes: 3.5 and later, so that non-important patches
do not need the Cc:stable anymore, but users who experience an issue
can easily spot them and ask for
On Fri, Jul 12, 2013 at 04:47:44PM -0400, Theodore Ts'o wrote:
On Fri, Jul 12, 2013 at 09:50:51PM +0200, Willy Tarreau wrote:
So probably we should incite patch contributors to add a specific
tag such as Fixes: 3.5 and later, so that non-important patches
do not need the Cc:stable anymore,
-Original Message-
From: Ben Hutchings [mailto:b...@decadent.org.uk]
Sent: Friday, July 12, 2013 4:17 PM
To: KY Srinivasan
Cc: gre...@linuxfoundation.org; linux-ker...@vger.kernel.org;
de...@linuxdriverproject.org; o...@aepfle.de; a...@canonical.com;
jasow...@redhat.com; Stable
On Fri, Jul 12, 2013 at 09:07:19PM +, KY Srinivasan wrote:
[...]
Well now it might look like a bug that you don't test the result
of wait_for_completion_timeout(). Maybe update the comment to
explain why it's OK to continue anyway?
I put in the comment in the patch explaining why it
On Fri, Jul 12, 2013 at 04:28:20PM -0400, Steven Rostedt wrote:
I would suspect that machines that allow unprivileged users would be
running distro kernels, and not the latest release from Linus, and thus
even a bug that can allow an unprivileged user to crash the kernel may
still be able to
On Thu, Jul 11, 2013 at 03:19:30PM -0700, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.9.10 release.
There are 15 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
On 07/12/2013 12:53 PM, Steven Rostedt wrote:
On Fri, 2013-07-12 at 12:44 -0700, Linus Torvalds wrote:
They can be useful for local notes (they can be very powerful for
certain workflows), but they won't be pulled and pushed by me.
Perhaps notes can be used as that reminder to send to
On 07/12/2013 01:33 PM, Greg Kroah-Hartman wrote:
Is it _really_ all that hard to remember what to mark for stable
inclusion? If you figure it out after you have committed the patch,
then just put a copy of it somewhere to remind yourself. That seems to
be what both David and I do with no
On Thursday, July 11, 2013 08:34:30 PM Greg Kroah-Hartman wrote:
On Thu, Jul 11, 2013 at 10:57:46PM -0400, John W. Linville wrote:
On Thu, Jul 11, 2013 at 08:50:23PM -0400, Theodore Ts'o wrote:
In any case, I've been very conservative in _not_ pushing bug fixes to
Linus after -rc3
The MinnowBoard uses an AR803x PHY with the PCH GBE which requires
special handling. Use the MinnowBoard PCI Subsystem ID to detect this
and add a pci_device_id.driver_data structure and functions to handle
platform setup.
The AR803x does not implement the RGMII 2ns TX clock delay in the trace
On Fri, 2013-07-12 at 17:58 -0700, Darren Hart wrote:
The MinnowBoard uses an AR803x PHY with the PCH GBE which requires
special handling. Use the MinnowBoard PCI Subsystem ID to detect this
and add a pci_device_id.driver_data structure and functions to handle
platform setup.
trivial comments
Hello,
On Fri, Jul 12, 2013 at 04:28:20PM -0400, Steven Rostedt wrote:
I would suspect that machines that allow unprivileged users would be
running distro kernels, and not the latest release from Linus, and thus
even a bug that can allow an unprivileged user to crash the kernel may
On Fri, Jul 12, 2013 at 05:58:07PM -0700, Darren Hart wrote:
The MinnowBoard uses an AR803x PHY with the PCH GBE which requires
special handling. Use the MinnowBoard PCI Subsystem ID to detect this
and add a pci_device_id.driver_data structure and functions to handle
platform setup.
The
On Fri, Jul 12, 2013 at 03:05:05PM -0700, Guenter Roeck wrote:
On Thu, Jul 11, 2013 at 03:19:30PM -0700, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.9.10 release.
There are 15 patches in this series, all will be posted as a response
to this one. If
On Sat, Jul 13, 2013 at 02:24:07AM +0200, Rafael J. Wysocki wrote:
On Thursday, July 11, 2013 08:34:30 PM Greg Kroah-Hartman wrote:
On Thu, Jul 11, 2013 at 10:57:46PM -0400, John W. Linville wrote:
On Thu, Jul 11, 2013 at 08:50:23PM -0400, Theodore Ts'o wrote:
In any case, I've been
At Thu, 11 Jul 2013 15:01:17 -0700,
Greg Kroah-Hartman wrote:
rant
I'm sitting on top of over 170 more patches that have been marked for
the stable releases right now that are not included in this set of
releases. The fact that there are this many patches for stable stuff
that are
At Thu, 11 Jul 2013 15:19:30 -0700,
Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.9.10 release.
There are 15 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
We have issued a Cash donation to you, kindly get back to us for more details.
Adrian Gillian Bayford Foundation. Subject Code: ADB980/09.
--
To unsubscribe from this list: send the line unsubscribe stable in
the body of a message to majord...@vger.kernel.org
More majordomo info at
At Thu, 11 Jul 2013 15:11:00 -0700,
Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.4.53 release.
There are 11 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
At Thu, 11 Jul 2013 15:20:29 -0700,
Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.0.86 release.
There are 8 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
On Sat, Jul 13, 2013 at 01:17:36PM +0900, Satoru Takeuchi wrote:
At Thu, 11 Jul 2013 15:20:29 -0700,
Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.0.86 release.
There are 8 patches in this series, all will be posted as a response
to this one. If
On Fri, 2013-07-12 at 18:17 -0700, Greg KH wrote:
On Fri, Jul 12, 2013 at 05:58:07PM -0700, Darren Hart wrote:
The MinnowBoard uses an AR803x PHY with the PCH GBE which requires
special handling. Use the MinnowBoard PCI Subsystem ID to detect this
and add a pci_device_id.driver_data
On Fri, 2013-07-12 at 18:10 -0700, Joe Perches wrote:
On Fri, 2013-07-12 at 17:58 -0700, Darren Hart wrote:
The MinnowBoard uses an AR803x PHY with the PCH GBE which requires
special handling. Use the MinnowBoard PCI Subsystem ID to detect this
and add a pci_device_id.driver_data structure
84 matches
Mail list logo
