netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: dhowells@redhat.com
Cc: netdev@vger.kernel.org, linux-afs@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] rxrpc: Rearrange headers
Date: Mon, 24 Jul 2017 16:17:34 -0700 (PDT)	[thread overview]
Message-ID: <20170724.161734.314010681276806847.davem@davemloft.net> (raw)
In-Reply-To: <150066178283.18902.5185801865257802317.stgit@warthog.procyon.org.uk>

From: David Howells <dhowells@redhat.com>
Date: Fri, 21 Jul 2017 19:29:42 +0100

> 
> Here's a pair of patches that rearrange some of the AF_RXRPC header files
> that are outside of the net/rxrpc/ directory:
> 
>  (1) The bits userspace need are moved to uapi/linux/rxrpc.h.  [Should this
>      be af_rxrpc.h instead, I wonder - but there doesn't seem to be
>      precedent for that in the other net UAPI headers.]
> 
>  (2) For the most part, the contents of rxrpc/packet.h are no longer used
>      outside of the AF_RXRPC module, so move them to net/rxrpc/protocol.h
>      with the exception of the standard abort codes which are exposed to
>      userspace when an abort occurs and the security index values which are
>      needed when constructing keys.
> 
> The patches can be found here also:
> 
> 	http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=rxrpc-rewrite
> 
> Tagged thusly:
> 
> 	git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> 	rxrpc-rewrite-20170721

Pulled, thanks David.

      parent reply	other threads:[~2017-07-24 23:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-21 18:29 [PATCH net-next 0/2] rxrpc: Rearrange headers David Howells
2017-07-21 18:29 ` [PATCH net-next 1/2] rxrpc: Expose UAPI definitions to userspace David Howells
2017-07-21 19:07   ` Joe Perches
2017-07-21 18:29 ` [PATCH net-next 2/2] rxrpc: Move the packet.h include file into net/rxrpc/ David Howells
2017-07-24 23:17 ` 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=20170724.161734.314010681276806847.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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 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).