All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Jason Baron <jbaron@redhat.com>
Subject: Re: linux-next: driver-core tree build warning
Date: Fri, 15 Aug 2008 22:34:32 -0700	[thread overview]
Message-ID: <20080816053432.GC20161@kroah.com> (raw)
In-Reply-To: <20080815125957.97930de0.sfr@canb.auug.org.au>

On Fri, Aug 15, 2008 at 12:59:57PM +1000, Stephen Rothwell wrote:
> Hi Greg,
> 
> Today's linux-next build (x86_64 allmodconfig) produced this warning:
> 
> In file included from include2/asm/string.h:4,
>                  from include/linux/string.h:19,
>                  from include/linux/dynamic_printk.h:4,
>                  from include/linux/kernel.h:19,
>                  from arch/x86/boot/memory.c:16:
> include2/asm/string_64.h:34:1: warning: "memcpy" redefined
> In file included from /scratch/sfr/next/arch/x86/boot/memory.c:15:
> arch/x86/boot/boot.h:231:1: warning: this is the location of the previous definition
> 
> Probably caused by commit 1b75321c2d0561d9ecfe3794fa939264f3eb7e26
> ("driver core: basic infrastructure for per-module dynamic debug
> messages") which added an include of linux/dynamic_printk.h to
> linux/kernel.h.

Wierd.  Jason, any thoughts?

thanks,

greg k-h

  reply	other threads:[~2008-08-16  5:36 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-15  2:59 linux-next: driver-core tree build warning Stephen Rothwell
2008-08-16  5:34 ` Greg KH [this message]
2008-08-18 19:09   ` Jason Baron
2008-08-18 22:35     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2009-05-01  5:21 Stephen Rothwell
     [not found] ` <20090501152144.500e619a.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2009-05-01  5:47   ` Greg KH
2009-05-01  5:47     ` Greg KH
2009-05-01  6:11     ` Greg KH
2009-05-01  7:11       ` Stephen Rothwell
2009-07-13  7:26 Stephen Rothwell
2009-07-13  7:28 ` Stephen Rothwell
2009-07-13  7:51   ` Stephen Rothwell
2009-07-13 17:18     ` Greg KH
2009-07-13 21:23       ` David Brownell
2009-07-13 21:27         ` Greg KH
2009-07-13 21:36         ` Greg KH
2009-07-14  0:44           ` Stephen Rothwell
2010-01-19  6:27 Stephen Rothwell
2010-01-19 21:04 ` Greg KH
2010-01-19 23:45   ` Stephen Rothwell
2010-01-20  6:25     ` Stephen Rothwell
2010-01-20  6:44       ` Stephen Rothwell
2010-01-21 23:10         ` Greg KH
2010-01-21 23:20           ` Stephen Rothwell
2010-01-29  7:21           ` Stephen Rothwell
2010-02-03  2:22             ` Greg KH
2010-02-03  3:29               ` Stephen Rothwell
2010-02-04  7:10               ` Stephen Rothwell

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=20080816053432.GC20161@kroah.com \
    --to=greg@kroah.com \
    --cc=jbaron@redhat.com \
    --cc=linux-next@vger.kernel.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 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.