From: Denys Fedoryshchenko <denys@visp.net.lb>
To: David Rientjes <rientjes@google.com>
Cc: Nithin Nayak Sujir <nsujir@broadcom.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Michael Chan <mchan@broadcom.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: Latest 3.6.6 are not compiling due tg3 network driver, hwmon_device_unregister
Date: Mon, 19 Nov 2012 08:59:37 +0200 [thread overview]
Message-ID: <d7418ec9ab1ae59a0ce5a101c6ff55e1@visp.net.lb> (raw)
In-Reply-To: <alpine.DEB.2.00.1211181441470.5080@chino.kir.corp.google.com>
On 2012-11-19 00:42, David Rientjes wrote:
> On Wed, 14 Nov 2012, Nithin Nayak Sujir wrote:
>
>> On 11/14/2012 07:30 PM, David Rientjes wrote:
>> > On Wed, 14 Nov 2012, Nithin Nayak Sujir wrote:
>> >
>> > > This was fixed by
>> > >
>> > > commit de0a41484c47d783dd4d442914815076aa2caac2
>> > > Author: Paul Gortmaker <paul.gortmaker@windriver.com>
>> > > Date: Mon Oct 1 11:43:49 2012 -0400
>> > >
>> > > tg3: unconditionally select HWMON support when tg3 is
>> enabled.
>> > >
>> > Would you mind submitting this for stable by following the
>> procedure
>> > described in Documentation/stable_kernel_rules.txt?
>> >
>>
>> Will do. Thank you for bringing this to our attention.
>>
>
> Thanks for submitting the patch to stable, Greg has queued it for the
> kernels he maintains. Denys, expect to see this fix in 3.6.8.
Thank you!
---
Denys Fedoryshchenko, Network Engineer, Virtual ISP S.A.L.
next prev parent reply other threads:[~2012-11-19 6:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 3:03 Denys Fedoryshchenko
2012-11-15 3:24 ` Nithin Nayak Sujir
2012-11-15 3:30 ` David Rientjes
2012-11-15 3:43 ` Nithin Nayak Sujir
2012-11-18 22:42 ` David Rientjes
2012-11-19 6:59 ` Denys Fedoryshchenko [this message]
2012-11-15 7:22 ` Nithin Sujir
2012-11-15 7:51 ` David Rientjes
2012-11-15 7:56 ` Mathias Krause
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d7418ec9ab1ae59a0ce5a101c6ff55e1@visp.net.lb \
--to=denys@visp.net.lb \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=nsujir@broadcom.com \
--cc=paul.gortmaker@windriver.com \
--cc=rientjes@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®