linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: David Howells <dhowells@redhat.com>
Cc: linux-m68k@vger.kernel.org, linux-arch@vger.kernel.org,
	Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH v2 01/11] m68k: switch to using the asm-generic auxvec.h
Date: Tue, 30 Oct 2012 16:21:25 +1000	[thread overview]
Message-ID: <508F71E5.2010101@snapgear.com> (raw)
In-Reply-To: <18903.1351507368@warthog.procyon.org.uk>

Hi David,

On 29/10/12 20:42, David Howells wrote:
> <gerg@snapgear.com> wrote:
>
>> diff --git a/arch/m68k/include/uapi/asm/Kbuild b/arch/m68k/include/uapi/asm/Kbuild
>> index 972bce1..588c3cc 100644
>> --- a/arch/m68k/include/uapi/asm/Kbuild
>> +++ b/arch/m68k/include/uapi/asm/Kbuild
>> @@ -2,7 +2,6 @@
>>   include include/uapi/asm-generic/Kbuild.asm
>>
>>   header-y += a.out.h
>> -header-y += auxvec.h
>>   header-y += byteorder.h
>>   header-y += cachectl.h
>>   header-y += fcntl.h
>
> Rather than removing header-y from the uapi Kbuild, you probably want to add a
> generic-y there.

Ok, will do. v3 coming up.

Thanks
Greg

  
------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
8 Gardner Close                             FAX:         +61 7 3217 5323
Milton, QLD, 4064, Australia                WEB: http://www.SnapGear.com

      parent reply	other threads:[~2012-10-30  6:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-29  5:49 [PATCH v2 00/11] m68k: use asm-generic headers when possible gerg
2012-10-29  5:49 ` gerg
2012-10-29  5:49 ` [PATCH v2 01/11] m68k: switch to using the asm-generic auxvec.h gerg
2012-10-29  5:49   ` gerg
2012-10-29  5:49 ` [PATCH v2 02/11] m68k: switch to using the asm-generic hw_irq.h gerg
2012-10-29  5:49   ` gerg
2012-10-29  5:49 ` [PATCH v2 03/11] m68k: switch to using the asm-generic shmparam.h gerg
2012-10-29  5:49   ` gerg
2012-10-29  5:49 ` [PATCH v2 04/11] m68k: switch to using the asm-generic msgbuf.h gerg
2012-10-29  5:49   ` gerg
2012-10-29  5:49 ` [PATCH v2 05/11] m68k: switch to using the asm-generic shmbuf.h gerg
2012-10-29  5:49 ` [PATCH v2 06/11] m68k: switch to using the asm-generic sembuf.h gerg
2012-10-29  5:49   ` gerg
2012-10-29  5:49 ` [PATCH v2 07/11] m68k: switch to using the asm-generic spinlock.h gerg
2012-10-29  5:49   ` gerg
2012-10-29  5:49 ` [PATCH v2 08/11] m68k: switch to using the asm-generic termbits.h gerg
2012-10-29  5:49   ` gerg
2012-10-29  5:49 ` [PATCH v2 09/11] m68k: switch to using the asm-generic termios.h gerg
2012-10-29  5:49 ` [PATCH v2 10/11] m68k: switch to using the asm-generic sockios.h gerg
2012-10-29  5:49   ` gerg
2012-10-29  5:49 ` [PATCH v2 11/11] m68k: switch to using the asm-generic socket.h gerg
2012-10-29  5:49   ` gerg
2012-10-29 10:42 ` [PATCH v2 01/11] m68k: switch to using the asm-generic auxvec.h David Howells
2012-10-29 10:42   ` David Howells
2012-10-30  6:21   ` Greg Ungerer [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=508F71E5.2010101@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=dhowells@redhat.com \
    --cc=gerg@uclinux.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-m68k@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).