From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [lm-sensors] 2.6.38-rc1/-2: applesmc lockdep warning
Date: Sat, 22 Jan 2011 21:18:14 +0000 [thread overview]
Message-ID: <20110122211814.GA22465@ericsson.com> (raw)
In-Reply-To: <20110122205254.GA2854@polaris.bitmath.org>
On Sat, Jan 22, 2011 at 03:52:54PM -0500, Henrik Rydberg wrote:
> > I can take it.
>
> Great, thanks.
>
> > Looks pretty straightforward. Do you think it is ready for upstream,
> > or should I wait for verification ?
>
> I was able to reproduce the problem, but a verification would still be
> good, just in case - if possible. AFAICT, it will be another week
> before rc3, so there seems to be no rush.
>
Ok, let's do it that way: I applied it, but won't submit to Linus yet.
This way we get some basic coverage through linux-next for a couple of days.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.38-rc1/-2: applesmc lockdep warning
Date: Sat, 22 Jan 2011 13:18:14 -0800 [thread overview]
Message-ID: <20110122211814.GA22465@ericsson.com> (raw)
In-Reply-To: <20110122205254.GA2854@polaris.bitmath.org>
On Sat, Jan 22, 2011 at 03:52:54PM -0500, Henrik Rydberg wrote:
> > I can take it.
>
> Great, thanks.
>
> > Looks pretty straightforward. Do you think it is ready for upstream,
> > or should I wait for verification ?
>
> I was able to reproduce the problem, but a verification would still be
> good, just in case - if possible. AFAICT, it will be another week
> before rc3, so there seems to be no rush.
>
Ok, let's do it that way: I applied it, but won't submit to Linus yet.
This way we get some basic coverage through linux-next for a couple of days.
Guenter
next prev parent reply other threads:[~2011-01-22 21:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 12:45 [lm-sensors] 2.6.38-rc1/-2: applesmc lockdep warning Stefan Richter
2011-01-22 12:45 ` Stefan Richter
2011-01-22 15:26 ` [lm-sensors] " Henrik Rydberg
2011-01-22 15:26 ` Henrik Rydberg
2011-01-22 20:00 ` [lm-sensors] " Henrik Rydberg
2011-01-22 20:00 ` Henrik Rydberg
2011-01-22 20:40 ` [lm-sensors] " Guenter Roeck
2011-01-22 20:40 ` Guenter Roeck
2011-01-22 20:52 ` [lm-sensors] " Henrik Rydberg
2011-01-22 20:52 ` Henrik Rydberg
2011-01-22 21:18 ` Guenter Roeck [this message]
2011-01-22 21:18 ` Guenter Roeck
2011-01-22 23:00 ` [lm-sensors] " Stefan Richter
2011-01-22 23:00 ` Stefan Richter
2011-01-23 13:38 ` [lm-sensors] " Henrik Rydberg
2011-01-23 13:38 ` Henrik Rydberg
2011-01-23 15:30 ` [lm-sensors] " Stefan Richter
2011-01-23 15:30 ` Stefan Richter
2011-01-23 16:55 ` [lm-sensors] " Guenter Roeck
2011-01-23 16:55 ` Guenter Roeck
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=20110122211814.GA22465@ericsson.com \
--to=guenter.roeck@ericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=rydberg@euromail.se \
--cc=stefanr@s5r6.in-berlin.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.