From: Linus Torvalds <torvalds@linux-foundation.org>
To: Michal Simek <michal.simek@petalogix.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
lkml <linux-arch@vger.kernel.org>,
microblaze-uclinux@itee.uq.edu.au, Arnd Bergmann <arnd@arndb.de>,
Andrew Morton <akpm@linux-foundation.org>,
John Williams <john.williams@petalogix.com>,
John Linn <John.Linn@xilinx.com>,
Stephen Neuendorffer <stephenn@xilinx.com>,
Thomas Gleixner <tglx@linutronix.de>,
Randy Dunlap <randy.dunlap@oracle.com>,
Ingo Molnar <mingo@elte.hu>, Peter Korsgaard <jacmet@sunsite.dk>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [GIT PULL, v3] Microblaze architecture (arch/microblaze/) support
Date: Mon, 13 Apr 2009 18:19:38 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0904131818050.26713@localhost.localdomain> (raw)
In-Reply-To: <49DC4024.6090800@petalogix.com>
On Wed, 8 Apr 2009, Michal Simek wrote:
>
> This repository contains Linux support for Xilinx Microblaze CPU.
>
> Please pull
> git://git.monstr.eu/linux-2.6-microblaze.git for-linus
So I pulled, but I notice that there's a few empty header files.
That looks intentional (they came in through a commit that says "headers
simple files - empty or redirect to asm-generic"), but it means that "make
distclean" will remove them. So if you really want an empty header file,
you should really make it not _completely_ empty - add a comment to it or
something.
Linus
next prev parent reply other threads:[~2009-04-14 1:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 6:11 Michal Simek
2009-04-14 1:19 ` Linus Torvalds [this message]
2009-04-14 1:39 ` Ingo Molnar
2009-04-14 12:45 ` Michal Simek
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=alpine.LFD.2.00.0904131818050.26713@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=John.Linn@xilinx.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.de \
--cc=jacmet@sunsite.dk \
--cc=john.williams@petalogix.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@petalogix.com \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
--cc=stephenn@xilinx.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®