From: Arnd Bergmann <arnd@arndb.de>
To: Firoz Khan <firoz.khan@linaro.org>
Cc: Michal Simek <michal.simek@xilinx.com>,
gregkh <gregkh@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <kstewart@linuxfoundation.org>,
y2038 Mailman List <y2038@lists.linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
Deepa Dinamani <deepa.kernel@gmail.com>,
Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Subject: Re: [PATCH 3/3] microblaze: uapi header and system call table file generation
Date: Tue, 25 Sep 2018 01:20:21 +0200 [thread overview]
Message-ID: <CAK8P3a0sYYzFyLLjfUuvWOijTsqpOnG2HGDA4nSRmR6YkM6W9A@mail.gmail.com> (raw)
In-Reply-To: <CALxhOngGqB2hY1MaEpTZvpgKTP9rwqbnMpgRKT9NQuZ4CXOcew@mail.gmail.com>
On Tue, Sep 18, 2018 at 9:12 AM Firoz Khan <firoz.khan@linaro.org> wrote:
>
> On 9 August 2018 at 12:42, Michal Simek <michal.simek@xilinx.com> wrote:
> > On 9.8.2018 07:27, Firoz Khan wrote:
> >> diff --git a/arch/microblaze/include/asm/Kbuild b/arch/microblaze/include/asm/Kbuild
> >> index fe6a6c6..99225ab 100644
> >> --- a/arch/microblaze/include/asm/Kbuild
> >> +++ b/arch/microblaze/include/asm/Kbuild
> >> @@ -30,3 +30,5 @@ generic-y += trace_clock.h
> >> generic-y += vga.h
> >> generic-y += word-at-a-time.h
> >> generic-y += xor.h
> >> +
> >> +generated-y += syscall_table.h
> >> \ No newline at end of file
> >
> > This doesn't look right.
>
> You mean I have to keep something like this?
> generic-y += xor.h
> -
> -generated-y += syscall_table.h
> \ No newline at end of file
> +generic-y += syscall_table.h
> \ No newline at end of file
The "\ No newline at end of file" line is produced by
git format-patch when you have accidentally removed
the newline at the end. Most editors don't even allow
you to do that, so I don't know what went wrong.
Arnd
next prev parent reply other threads:[~2018-09-24 23:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 5:27 [PATCH 0/3] System call table generation support Firoz Khan
2018-08-09 5:27 ` Firoz Khan
2018-08-09 5:27 ` [PATCH 1/3] microblaze: Replace NR_syscalls macro from asm/unistd.h Firoz Khan
2018-08-09 5:27 ` Firoz Khan
2018-08-09 6:48 ` Michal Simek
2018-08-09 6:48 ` Michal Simek
2018-09-18 6:37 ` Firoz Khan
2018-09-18 6:37 ` Firoz Khan
2018-10-02 7:07 ` Michal Simek
2018-10-02 7:07 ` Michal Simek
2018-10-03 5:09 ` Firoz Khan
2018-10-03 5:09 ` Firoz Khan
2018-08-09 5:27 ` [PATCH 2/3] microblaze: Added system call table generation support Firoz Khan
2018-08-09 5:27 ` Firoz Khan
2018-08-09 7:05 ` Michal Simek
2018-08-09 7:05 ` Michal Simek
2018-09-18 6:50 ` Firoz Khan
2018-09-18 6:50 ` Firoz Khan
2018-08-09 5:27 ` [PATCH 3/3] microblaze: uapi header and system call table file generation Firoz Khan
2018-08-09 5:27 ` Firoz Khan
2018-08-09 7:12 ` Michal Simek
2018-08-09 7:12 ` Michal Simek
2018-09-18 7:12 ` Firoz Khan
2018-09-18 7:12 ` Firoz Khan
2018-09-24 23:20 ` Arnd Bergmann [this message]
2018-09-24 23:20 ` Arnd Bergmann
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=CAK8P3a0sYYzFyLLjfUuvWOijTsqpOnG2HGDA4nSRmR6YkM6W9A@mail.gmail.com \
--to=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=firoz.khan@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.juszkiewicz@linaro.org \
--cc=michal.simek@xilinx.com \
--cc=pombredanne@nexb.com \
--cc=tglx@linutronix.de \
--cc=y2038@lists.linaro.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).