> On 04 May 2015 at 23:30 "Rafael J. Wysocki" wrote:
>
>
> On Saturday, May 02, 2015 06:01:21 PM Fabian Frederick wrote:
> > EXPORT macro must be placed directly after functions.
> > See Documentation/CodingStyle Chapter 6
>
> Well, why is this change an improvement?
>
> Yes, it makes an old
On 04 May 2015 at 23:30 Rafael J. Wysocki r...@rjwysocki.net wrote:
On Saturday, May 02, 2015 06:01:21 PM Fabian Frederick wrote:
EXPORT macro must be placed directly after functions.
See Documentation/CodingStyle Chapter 6
Well, why is this change an improvement?
Yes, it makes an
On Saturday, May 02, 2015 06:01:21 PM Fabian Frederick wrote:
> EXPORT macro must be placed directly after functions.
> See Documentation/CodingStyle Chapter 6
Well, why is this change an improvement?
Yes, it makes an old file follow the new(er) Documentation/CodingStyl,
but what exactly is the
On Saturday, May 02, 2015 06:01:21 PM Fabian Frederick wrote:
EXPORT macro must be placed directly after functions.
See Documentation/CodingStyle Chapter 6
Well, why is this change an improvement?
Yes, it makes an old file follow the new(er) Documentation/CodingStyl,
but what exactly is the
EXPORT macro must be placed directly after functions.
See Documentation/CodingStyle Chapter 6
Signed-off-by: Fabian Frederick
---
drivers/pnp/driver.c | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/drivers/pnp/driver.c b/drivers/pnp/driver.c
index 153a493..b690e6b
EXPORT macro must be placed directly after functions.
See Documentation/CodingStyle Chapter 6
Signed-off-by: Fabian Frederick f...@skynet.be
---
drivers/pnp/driver.c | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/drivers/pnp/driver.c b/drivers/pnp/driver.c
index
6 matches
Mail list logo
