From: David Miller <davem@davemloft.net>
To: randy.dunlap@oracle.com
Cc: netdev@vger.kernel.org, patrick.ohly@intel.com
Subject: Re: [PATCH] timestamping: fix example build
Date: Mon, 15 Mar 2010 16:05:12 -0700 (PDT) [thread overview]
Message-ID: <20100315.160512.218598212.davem@davemloft.net> (raw)
In-Reply-To: <4B9B214F.4040005@oracle.com>
From: Randy Dunlap <randy.dunlap@oracle.com>
Date: Fri, 12 Mar 2010 21:23:27 -0800
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Fix Makefiles so that Documentation/networking/timestamping/timestamping.c
> will build when using the CONFIG_BUILD_DOCSRC kconfig option.
> (timestamping.c does not build currently with its simple Makefile.)
>
> Also fix printf format warnings.
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> Cc: Patrick Ohly <patrick.ohly@intel.com>
Applied, thanks Randy.
prev parent reply other threads:[~2010-03-15 23:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-13 5:23 [PATCH] timestamping: fix example build Randy Dunlap
2010-03-15 23:05 ` David Miller [this message]
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=20100315.160512.218598212.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=patrick.ohly@intel.com \
--cc=randy.dunlap@oracle.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;
as well as URLs for NNTP newsgroup(s).