From: "Gujare, Rupesh" <Rupesh.Gujare@atmel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: linux-next: Tree for Aug 9 (staging/ozwpan)
Date: Sun, 11 Aug 2013 09:04:00 +0000 [thread overview]
Message-ID: <CB57019DFBA97B45884DCA732411B955341FA6C8@hnombx02.corp.atmel.com> (raw)
In-Reply-To: <5206C9AB.8050706@infradead.org>
________________________________________
From: Randy Dunlap [rdunlap@infradead.org]
Sent: 11 August 2013 00:15
To: Stephen Rothwell
Cc: linux-next@vger.kernel.org; linux-kernel@vger.kernel.org; devel@driverdev.osuosl.org; Gujare, Rupesh; Greg Kroah-Hartman
Subject: Re: linux-next: Tree for Aug 9 (staging/ozwpan)
On 08/10/13 15:15, Randy Dunlap wrote:
> On 08/08/13 23:15, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20130808:
>>
>> *crickets*
>>
>
> on i386:
>
> ERROR: "__divdi3" [drivers/staging/ozwpan/ozwpan.ko] undefined!
>
2 occurrences of this in oz_hcd_heartbeat().
>
>
> Apologies if this has already been reported/fixed.
>
Yes, It had been already been fixed here :-
http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2013-August/040091.html
I have been waiting for Greg to apply this patch to his tree.
--
Regards,
Rupesh Gujare
next prev parent reply other threads:[~2013-08-11 9:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 6:15 linux-next: Tree for Aug 9 Stephen Rothwell
2013-08-09 16:53 ` Randy Dunlap
2013-08-09 23:46 ` Stephen Rothwell
2013-08-10 22:15 ` linux-next: Tree for Aug 9 (staging/ozwpan) Randy Dunlap
2013-08-10 23:15 ` Randy Dunlap
2013-08-11 9:04 ` Gujare, Rupesh [this message]
2013-08-12 6:22 ` Greg Kroah-Hartman
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=CB57019DFBA97B45884DCA732411B955341FA6C8@hnombx02.corp.atmel.com \
--to=rupesh.gujare@atmel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).