public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: David Howells <dhowells@redhat.com>
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Disintegrate UAPI for mmc
Date: Fri, 12 Oct 2012 09:12:55 -0400	[thread overview]
Message-ID: <87626f3kbs.fsf@octavius.laptop.org> (raw)
In-Reply-To: <30707.1349789429@warthog.procyon.org.uk> (David Howells's message of "Tue, 09 Oct 2012 14:30:29 +0100")

Hi David,

On Tue, Oct 09 2012, David Howells wrote:
> Can you merge the following branch into the mmc tree please.
>
> This is to complete part of the Userspace API (UAPI) disintegration for which
> the preparatory patches were pulled recently.  After these patches, userspace
> headers will be segregated into:
>
> 	include/uapi/linux/.../foo.h
>
> for the userspace interface stuff, and:
>
> 	include/linux/.../foo.h
>
> for the strictly kernel internal stuff.
>
> ---
> The following changes since commit 9e2d8656f5e8aa214e66b462680cf86b210b74a8:
>
>   Merge branch 'akpm' (Andrew's patch-bomb) (2012-10-09 16:23:15 +0900)
>
> are available in the git repository at:
>
>
>   git://git.infradead.org/users/dhowells/linux-headers.git tags/disintegrate-mmc-20121009
>
> for you to fetch changes up to ad1cfdcef1378adc7215a74772f7d06c4cc6ef50:
>
>   UAPI: (Scripted) Disintegrate include/linux/mmc (2012-10-09 09:48:45 +0100)

Thanks, I've sent this to Linus now.

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

      reply	other threads:[~2012-10-12 13:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-09 13:30 [GIT PULL] Disintegrate UAPI for mmc David Howells
2012-10-12 13:12 ` Chris Ball [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=87626f3kbs.fsf@octavius.laptop.org \
    --to=cjb@laptop.org \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@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