All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Pavel Emelyanov <xemul@parallels.com>
Cc: David Miller <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Add unix_diag.h to kernel userspace headers
Date: Sun, 22 Jan 2012 09:38:29 -0800	[thread overview]
Message-ID: <20120122093829.1f6d8ad9@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <4F1B0043.1000304@parallels.com>

On Sat, 21 Jan 2012 22:13:23 +0400
Pavel Emelyanov <xemul@parallels.com> wrote:

> On 01/21/2012 12:41 AM, Stephen Hemminger wrote:
> > The change to use provide unix domain diag information in iproute2 means that
> > an additional header file has to be added to the kbuild header export list.
> > This ensures that any changes to the header file get picked up in future merges.
> 
> It should be already there since 6a1c9522 (unix_diag: Include unix_diag.h into header-y target)

Yup, was looking at old tree.

      reply	other threads:[~2012-01-22 17:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-20 20:41 Add unix_diag.h to kernel userspace headers Stephen Hemminger
2012-01-21 18:13 ` Pavel Emelyanov
2012-01-22 17:38   ` Stephen Hemminger [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=20120122093829.1f6d8ad9@nehalam.linuxnetplumber.net \
    --to=shemminger@vyatta.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=xemul@parallels.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 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.