All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Helsley <matthltc@us.ibm.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] Re: [PATCH] bug fix to include/linux/cn_proc.h for 2.6.16-rc5
Date: Thu, 16 Mar 2006 21:03:52 +0000	[thread overview]
Message-ID: <1142543033.24621.209.camel@stark> (raw)
In-Reply-To: <1142312124.24621.82.camel@stark>

[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]

On Thu, 2006-03-16 at 10:44 -0800, Nishanth Aravamudan wrote:
> On 16.03.2006 [09:56:13 -0800], Narasimha Sharoff wrote:
<snip>
> > I do not know how the header files end up in /usr/include/linux
> > directory. Is there a standard process followed while packaging or is
> > this distro specific? Can someone forward me a pointer?
> 
> Distro specific, there's probably a package you can find that put the
> header there (apt-file search filename or dpkg -S filename can help on
> Debian-based distros). I would figure out why it's there (and if it
> should be). Complain to the connector folks about it, as well (or just
> bring it to their attention).

	Perhaps contacting the package maintainer is the correct approach. Have
them remove the #include line from cn_proc.h.

	cn_proc.h should be available to userspace in some form. The event
structures it sends to userspace are defined there. That structure
includes a struct timespec as a timestamp.

	The way I see it, this issue isn't related to connectors. It's related
to process events which send a timestamp with the event to userspace. It
happens to use a connector to send the events. I included time.h because
I needed the timespec struct and getnstimestamp().

Cheers,
	-Matt Helsley


[-- Attachment #2: Type: text/plain, Size: 168 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2006-03-16 21:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-14  4:55 [KJ] Re: [PATCH] bug fix to include/linux/cn_proc.h for 2.6.16-rc5 Matt Helsley
2006-03-14  5:01 ` Matthew L Helsley
2006-03-14  7:17 ` Narasimha Sharoff
2006-03-14 14:38 ` Nishanth Aravamudan
2006-03-14 19:19 ` Matt Helsley
2006-03-16 17:56 ` Narasimha Sharoff
2006-03-16 18:44 ` Nishanth Aravamudan
2006-03-16 21:03 ` Matt Helsley [this message]
2006-03-28 23:29 ` Matt Helsley

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=1142543033.24621.209.camel@stark \
    --to=matthltc@us.ibm.com \
    --cc=kernel-janitors@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 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.