public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
	linux-kernel@vger.kernel.org, geert@linux-m68k.org,
	dhowells@redhat.com
Subject: Re: [PATCH] get rid of the last symlink in uml build
Date: Mon, 06 Oct 2008 17:03:30 +1000	[thread overview]
Message-ID: <48E9B842.1020303@snapgear.com> (raw)
In-Reply-To: <20081217171800.GA5436@uranus.ravnborg.org>

Hi Sam,

Sam Ravnborg wrote:
> On Wed, Dec 17, 2008 at 05:02:57PM +0000, Al Viro wrote:
>> 	BTW, after taking a look at the remaing asm-*...
>>
>> * frv, m32r and h8300 should be as trivial as git mv
> 
> Yep - I already have positive feedback from arch maintainers that
> they will fix it in the -rc1 timeframe.
> 
>> * m68k has a bit of extra PITA - we need to clean up two non-trivial
>>   includes from m68knommu (pci.h and setup.h) first, then it's a matter
>>   of git mv, adding arch/m68k/include to search path on m68knommu and
>>   removal of dummy headers from the latter.
> 
> I took a different route here and unified the headers for m68k and m68knommu
> under arch/m68k/include/asm
> It was based on a script originally developed by Arnd Bergmann.
> 
> Geert already acked it, and I expect Greg to apply it in the -rc1 timeframe.

I have been away for the last few weeks, so I haven't looked at this
at all yet. I will over the next few days though.

Regards
Greg



> http://marc.info/?l=linux-kbuild&m=122927123805002&w=2 has Geert's ack,
> but original patch did not hit marc?!?
> 
>> * xtensa is already moved in linux-next
> Yes.
> 
> 
>> * arm seems to be lacking the final push for few remaining headers; presumably
>>   will happen eventually
> rmk knows it and takes care.
> 
>> * mn10300 is playing with symlinks - the last one to do that for headers,
>>   AFAICS.
>>
>> I've thrown together a patch series on top of linux-next doing m68k and
>> mn10300.  *WARNING* - it's completely untested, basically about half an
>> hour diversion from sifting through the mailbox for missed VFS patches.
>> And that half and hour did *not* include anything resembling building
>> the resulting tree.  So take that with a trainload of salt.
> Thanks Al.
> I will take a closer look at the mn10300 bits and send them to David
> in due time.
> 
> 	Sam
> 

-- 
------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear, a McAfee Company                  PHONE:       +61 7 3435 2888
825 Stanley St,                             FAX:         +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia         WEB: http://www.SnapGear.com

  reply	other threads:[~2009-01-12  7:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17  6:12 [PATCH] get rid of the last symlink in uml build Al Viro
2008-12-17  7:26 ` Sam Ravnborg
2008-12-17  8:37   ` Al Viro
2008-12-17  8:55     ` Sam Ravnborg
2008-12-17  9:10       ` Al Viro
2008-12-17 11:27         ` Sam Ravnborg
2008-12-17 17:02           ` Al Viro
2008-12-17 17:18             ` Sam Ravnborg
2008-10-06  7:03               ` Greg Ungerer [this message]
2009-01-12 10:16                 ` Sam Ravnborg
2008-12-17 17:33               ` Al Viro
2008-12-17 17:35               ` David Howells

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=48E9B842.1020303@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=dhowells@redhat.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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