public inbox for linux-input@vger.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: Joe Perches <joe@perches.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-input@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 0/1] Input: inline macros for MODULE_LICENSE, etc
Date: Tue, 26 Dec 2017 19:10:48 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1712261906440.5715@hadrien> (raw)
In-Reply-To: <1514311471.3468.8.camel@perches.com>



On Tue, 26 Dec 2017, Joe Perches wrote:

> On Tue, 2017-12-26 at 18:05 +0100, Julia Lawall wrote:
> > Inline macro for MODULE_LICENSE to make the license information easy to
> > find, eg with grep.  Inline the other module-related macros at the same
> > time.
>
> Perhaps it'd be better to not make this
> dependent on a MODULE_LICENSE use, but allow
> any #define foo/#define MODULE_<FOO> foo
> where foo is used once to be converted.

Well, I wanted something that could be checked in a finite (small) amount
of time...  There seemed to be a slightly more compelling argument for
inlining the license, so I decided to focus on that.  What you suggested
resulted in around 5000 lines of patch code, mostly inlining authors and
descriptions.

But maybe you have already done the things done in my patch and it hasn't
been picked up yet?

julia

      reply	other threads:[~2017-12-26 18:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-26 17:05 [PATCH 0/1] Input: inline macros for MODULE_LICENSE, etc Julia Lawall
2017-12-26 17:05 ` [PATCH 1/1] " Julia Lawall
2017-12-26 17:52 ` [PATCH 0/1] " Joe Perches
2017-12-26 17:56   ` Julia Lawall
2017-12-26 18:04 ` Joe Perches
2017-12-26 18:10   ` Julia Lawall [this message]

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=alpine.DEB.2.20.1712261906440.5715@hadrien \
    --to=julia.lawall@lip6.fr \
    --cc=dmitry.torokhov@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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