From: Joe Perches <joe@perches.com> To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> Cc: Nick Desaulniers <ndesaulniers@google.com>, Sedat Dilek <sedat.dilek@gmail.com>, "Paul E . McKenney" <paulmck@kernel.org>, Steven Rostedt <rostedt@goodmis.org>, Mathieu Desnoyers <mathieu.desnoyers@efficios.com>, Lai Jiangshan <jiangshanlai@gmail.com>, Josh Triplett <josh@joshtriplett.org>, Kees Cook <keescook@chromium.org>, LKML <linux-kernel@vger.kernel.org>, rcu@vger.kernel.org, Clang-Built-Linux ML <clang-built-linux@googlegroups.com>, Michael Ellerman <mpe@ellerman.id.au>, Benjamin Herrenschmidt <benh@kernel.crashing.org>, Paul Mackerras <paulus@samba.org>, linuxppc-dev@lists.ozlabs.org Subject: Re: [RFC PATCH next-20200930] treewide: Convert macro and uses of __section(foo) to __section("foo") Date: Thu, 01 Oct 2020 12:05:38 -0700 [thread overview] Message-ID: <657119d71970e33d599b3fe9e596e8f133449d85.camel@perches.com> (raw) In-Reply-To: <CANiq72mSjs4myQQtUoegjRggjTx9UF70nAcWoXRoTeLMOuf0xQ@mail.gmail.com> On Thu, 2020-10-01 at 12:15 +0200, Miguel Ojeda wrote: > Hi Joe, Buenas Miguel. > On Thu, Oct 1, 2020 at 12:56 AM Joe Perches <joe@perches.com> wrote: > > So I installed the powerpc cross compiler, and > > nope, that doesn't work, it makes a mess. > > Thanks a lot for reviving the script and sending the treewide cleanup! No charge... I think the end result is cleaner and more obvious. > > So it looks like the best option is to exclude these > > 2 files from conversion. > > Agreed. Nevertheless, is there any reason arch/powerpc/* should not be > compiling cleanly with compiler.h? (CC'ing the rest of the PowerPC > reviewers and ML). That's not a can of worms I care to open. Perhaps the powerpc folk can do some fishing.
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com> To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> Cc: Kees Cook <keescook@chromium.org>, "Paul E . McKenney" <paulmck@kernel.org>, Nick Desaulniers <ndesaulniers@google.com>, Lai Jiangshan <jiangshanlai@gmail.com>, Josh Triplett <josh@joshtriplett.org>, Steven Rostedt <rostedt@goodmis.org>, LKML <linux-kernel@vger.kernel.org>, rcu@vger.kernel.org, Clang-Built-Linux ML <clang-built-linux@googlegroups.com>, Mathieu Desnoyers <mathieu.desnoyers@efficios.com>, Sedat Dilek <sedat.dilek@gmail.com>, Paul Mackerras <paulus@samba.org>, linuxppc-dev@lists.ozlabs.org Subject: Re: [RFC PATCH next-20200930] treewide: Convert macro and uses of __section(foo) to __section("foo") Date: Thu, 01 Oct 2020 12:05:38 -0700 [thread overview] Message-ID: <657119d71970e33d599b3fe9e596e8f133449d85.camel@perches.com> (raw) In-Reply-To: <CANiq72mSjs4myQQtUoegjRggjTx9UF70nAcWoXRoTeLMOuf0xQ@mail.gmail.com> On Thu, 2020-10-01 at 12:15 +0200, Miguel Ojeda wrote: > Hi Joe, Buenas Miguel. > On Thu, Oct 1, 2020 at 12:56 AM Joe Perches <joe@perches.com> wrote: > > So I installed the powerpc cross compiler, and > > nope, that doesn't work, it makes a mess. > > Thanks a lot for reviving the script and sending the treewide cleanup! No charge... I think the end result is cleaner and more obvious. > > So it looks like the best option is to exclude these > > 2 files from conversion. > > Agreed. Nevertheless, is there any reason arch/powerpc/* should not be > compiling cleanly with compiler.h? (CC'ing the rest of the PowerPC > reviewers and ML). That's not a can of worms I care to open. Perhaps the powerpc folk can do some fishing.
next prev parent reply other threads:[~2020-10-01 19:05 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-29 19:22 [PATCH] srcu: avoid escaped section names Nick Desaulniers 2020-09-29 19:22 ` Nick Desaulniers 2020-09-29 19:25 ` [PATCH v2] " Nick Desaulniers 2020-09-29 23:45 ` Kees Cook 2020-09-30 16:27 ` Nathan Chancellor 2020-09-30 16:41 ` Sedat Dilek 2020-09-30 18:57 ` Joe Perches 2020-09-30 19:16 ` [RFC PATCH next-20200930] treewide: Convert macro and uses of __section(foo) to __section("foo") Joe Perches 2020-09-30 21:40 ` Nick Desaulniers 2020-09-30 22:06 ` Joe Perches 2020-09-30 22:12 ` Joe Perches 2020-09-30 22:20 ` Nick Desaulniers 2020-09-30 22:25 ` Joe Perches 2020-09-30 22:56 ` Joe Perches 2020-10-01 10:15 ` Miguel Ojeda 2020-10-01 10:15 ` Miguel Ojeda 2020-10-01 19:05 ` Joe Perches [this message] 2020-10-01 19:05 ` Joe Perches 2020-10-01 19:39 ` Segher Boessenkool 2020-10-01 19:39 ` Segher Boessenkool 2020-10-01 20:19 ` Joe Perches 2020-10-05 18:36 ` Nick Desaulniers 2020-10-05 18:36 ` Nick Desaulniers 2020-10-05 18:46 ` Joe Perches 2020-10-05 18:46 ` Joe Perches 2020-10-06 0:34 ` Joel Stanley 2020-10-06 0:34 ` Joel Stanley 2020-10-06 3:22 ` Joe Perches 2020-10-06 3:22 ` Joe Perches 2020-09-30 20:40 ` [PATCH v2] srcu: avoid escaped section names Paul E. McKenney 2020-09-30 20:55 ` Nick Desaulniers 2020-10-02 20:51 ` Paul E. McKenney 2020-10-05 18:29 ` Nick Desaulniers 2020-10-05 18:38 ` Sedat Dilek 2020-10-05 18:49 ` Paul E. McKenney 2020-10-06 6:56 ` Nathan Chancellor 2020-10-07 21:05 ` Paul E. McKenney
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=657119d71970e33d599b3fe9e596e8f133449d85.camel@perches.com \ --to=joe@perches.com \ --cc=benh@kernel.crashing.org \ --cc=clang-built-linux@googlegroups.com \ --cc=jiangshanlai@gmail.com \ --cc=josh@joshtriplett.org \ --cc=keescook@chromium.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=mathieu.desnoyers@efficios.com \ --cc=miguel.ojeda.sandonis@gmail.com \ --cc=mpe@ellerman.id.au \ --cc=ndesaulniers@google.com \ --cc=paulmck@kernel.org \ --cc=paulus@samba.org \ --cc=rcu@vger.kernel.org \ --cc=rostedt@goodmis.org \ --cc=sedat.dilek@gmail.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.