From: Dave Jones <davej@redhat.com>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: Jiri Slaby <jslaby@suse.cz>, trinity@vger.kernel.org
Subject: Re: [PATCH 1/3] use config.h in USE_* users
Date: Thu, 6 Jun 2013 12:17:42 -0400 [thread overview]
Message-ID: <20130606161742.GA13108@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1306061210120.23627@vincent-weaver-1.um.maine.edu>
On Thu, Jun 06, 2013 at 12:14:34PM -0400, Vince Weaver wrote:
> On Wed, 5 Jun 2013, Dave Jones wrote:
> >
> > For "we don't care about out of tree compatibility" like this, carrying our
> > own copy of the header sounds like probably the best option.
>
> So something like the following patch? I stuck perf_event.h in the
> syscalls directory, not sure if it should go in include instead?
syscalls/ works. We already have setsockopt.h there.
We can also drop some bits from compat.h if we do this.
Want to respin that diff with that ? (or send an incremental, I don't care which)
Dave
next prev parent reply other threads:[~2013-06-06 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1370339304-26492-1-git-send-email-jslaby@suse.cz>
2013-06-04 9:50 ` [PATCH 1/3] use config.h in USE_* users Jiri Slaby
2013-06-05 19:14 ` Vince Weaver
2013-06-05 19:18 ` Dave Jones
2013-06-06 16:14 ` Vince Weaver
2013-06-06 16:17 ` Dave Jones [this message]
2013-06-08 15:51 ` Vince Weaver
2013-06-09 2:38 ` Vince Weaver
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=20130606161742.GA13108@redhat.com \
--to=davej@redhat.com \
--cc=jslaby@suse.cz \
--cc=trinity@vger.kernel.org \
--cc=vincent.weaver@maine.edu \
/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