Re: [PATCH 0/4] sh: fix up modular use in non-modular code

2016-07-02 Thread Paul Gortmaker
[Re: [PATCH 0/4] sh: fix up modular use in non-modular code] On 02/06/2016 (Thu 15:54) Yoshinori Sato wrote: > On Fri, 27 May 2016 01:53:34 +0900, > Rich Felker wrote: > > > > On Thu, May 26, 2016 at 12:45:57PM -0400, Paul Gortmaker wrote: > > > [[PATCH 0/4] sh

Re: [PATCH 0/4] sh: fix up modular use in non-modular code

2016-06-01 Thread Yoshinori Sato
On Fri, 27 May 2016 01:53:34 +0900, Rich Felker wrote: > > On Thu, May 26, 2016 at 12:45:57PM -0400, Paul Gortmaker wrote: > > [[PATCH 0/4] sh: fix up modular use in non-modular code] On 22/04/2016 (Fri > > 14:07) Paul Gortmaker wrote: > > > > > For anyone n

Re: [PATCH 0/4] sh: fix up modular use in non-modular code

2016-05-26 Thread Rich Felker
On Thu, May 26, 2016 at 12:45:57PM -0400, Paul Gortmaker wrote: > [[PATCH 0/4] sh: fix up modular use in non-modular code] On 22/04/2016 (Fri > 14:07) Paul Gortmaker wrote: > > > For anyone new to the underlying goal of this cleanup, we are trying to > > make kernel cod

Re: [PATCH 0/4] sh: fix up modular use in non-modular code

2016-05-26 Thread Paul Gortmaker
[[PATCH 0/4] sh: fix up modular use in non-modular code] On 22/04/2016 (Fri 14:07) Paul Gortmaker wrote: > For anyone new to the underlying goal of this cleanup, we are trying to > make kernel code consistent with the Makefiles/Kconfigs that control them. Ping -- wondering if there a

[PATCH 0/4] sh: fix up modular use in non-modular code

2016-04-22 Thread Paul Gortmaker
For anyone new to the underlying goal of this cleanup, we are trying to make kernel code consistent with the Makefiles/Kconfigs that control them. This means not using modular functions/macros for code that can never be built as a module. Some of the other downfalls this leads to are: (1) it is