[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a3xxu1wFKdsAHfuy2vpLigbuPR878mq75hh8HR=Tg=7LA@mail.gmail.com>
Date: Wed, 12 Feb 2020 09:45:04 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Michal Simek <michal.simek@...inx.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Michal Simek <monstr@...str.eu>, git@...inx.com,
Firoz Khan <firoz.khan@...aro.org>,
Stefan Asserhall <stefan.asserhall@...inx.com>
Subject: Re: [PATCH] microblaze: Fix unistd_32.h generation format
On Wed, Feb 12, 2020 at 9:42 AM Michal Simek <michal.simek@...inx.com> wrote:
>
> On 12. 02. 20 9:38, Arnd Bergmann wrote:
> > On Wed, Feb 12, 2020 at 8:56 AM Michal Simek <michal.simek@...inx.com> wrote:
> >>
> >> Generated files are also checked by sparse that's why add newline
> >> to remove sparse (C=1) warning:
> >> ./arch/microblaze/include/generated/uapi/asm/unistd_32.h:438:45:
> >> warning: no newline at end of file
> >>
> >> Signed-off-by: Michal Simek <michal.simek@...inx.com>
> >> Reviewed-by: Stefan Asserhall <stefan.asserhall@...inx.com>
> >
> > Acked-by: Arnd Bergmann <arnd@...db.de>
> >
> > The patch looks good, but if you don't mind respinning it, could respin
> > it to do the same thing for all architectures at once? I see that some
> > already have it, but most don't.
>
> I have not a problem to do so. I expect that this can be taken via your
> tree that I can create only one patch. If this should go via
> architectures tree would be better to create separate one.
Yes, I can take that into the asm-generic tree, or maybe you can just send it
to Andrew Morton.
Arnd
Powered by blists - more mailing lists