From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
target-devel <target-devel@vger.kernel.org>,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>
Subject: Re: linux-next: Tree for Dec 19 (target)
Date: Thu, 19 Dec 2013 21:44:22 +0100 [thread overview]
Message-ID: <CAMuHMdXdz5numoe_8SzYy_AN4++c2c_uqPtbdhq9kzTdLN=7+g@mail.gmail.com> (raw)
In-Reply-To: <52B349B5.6090200@infradead.org>
On Thu, Dec 19, 2013 at 8:32 PM, Randy Dunlap <rdunlap@infradead.org> wrote:
> On 12/18/13 21:51, Stephen Rothwell wrote:
>> Changes since 20131218:
> on i386:
>
> drivers/built-in.o: In function `target_alua_state_check':
> (.text+0x3fc859): undefined reference to `__udivdi3'
I believe this is already fixed in today's tree (it also happened on m68k
and mips).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2013-12-19 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 5:51 linux-next: Tree for Dec 19 Stephen Rothwell
2013-12-19 19:32 ` linux-next: Tree for Dec 19 (target) Randy Dunlap
2013-12-19 20:44 ` Geert Uytterhoeven [this message]
2013-12-19 21:30 ` Nicholas A. Bellinger
2013-12-19 20:44 ` linux-next: Tree for Dec 19 (6lowpan) Randy Dunlap
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='CAMuHMdXdz5numoe_8SzYy_AN4++c2c_uqPtbdhq9kzTdLN=7+g@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=target-devel@vger.kernel.org \
/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).