From: Lee Jones <lee@kernel.org>
To: Nick Alcock <nick.alcock@oracle.com>
Cc: mcgrof@kernel.org, linux-modules@vger.kernel.org,
linux-kernel@vger.kernel.org,
Hitomi Hasegawa <hasegawa-hitomi@fujitsu.com>,
Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH 26/27] mfd: remove MODULE_LICENSE in non-modules
Date: Wed, 8 Mar 2023 14:31:37 +0000 [thread overview]
Message-ID: <20230308143137.GQ9667@google.com> (raw)
In-Reply-To: <87bkl35r2t.fsf@esperi.org.uk>
On Wed, 08 Mar 2023, Nick Alcock wrote:
> On 8 Mar 2023, Lee Jones uttered the following:
>
> > On Wed, 08 Mar 2023, Nick Alcock wrote:
> >
> >> >> drivers/mfd/omap-usb-host.c | 1 -
> >> >> drivers/mfd/omap-usb-tll.c | 1 -
> >> >> drivers/mfd/twl4030-audio.c | 1 -
> >> >> drivers/mfd/twl6040.c | 1 -
> >> >> 4 files changed, 4 deletions(-)
> [...]
> >> For now, I'll split this one into four and mail it out again: coming
> >> shortly.
> >
> > If you haven't sent it out already, 2 will be fine.
> >
> > mfd: omap: ...
> > mfd: twl: ...
>
> I'm trying to automate this whole thing (since I've had to resplit it a
> dozen times already), and even making mfd a special case that wants
> splitting finer than by subsystem, I honestly have no idea how to
> automatically determine a split like *that*. I can't split on file, on
> subsystem, on dashes in the names... I think I'd have to literally parse
> the makefile to figure out which things belonged together in commits,
> and that's getting ridiculous even for me.
>
> So, if you don't mind, I'd rather do it by subsystem or by file :)
File is fine.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-03-08 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230224150811.80316-1-nick.alcock@oracle.com>
2023-02-24 15:08 ` [PATCH 26/27] mfd: remove MODULE_LICENSE in non-modules Nick Alcock
2023-03-03 10:52 ` Lee Jones
2023-03-08 12:32 ` Nick Alcock
2023-03-08 13:04 ` Lee Jones
2023-03-08 13:07 ` Nick Alcock
2023-03-08 14:31 ` Lee Jones [this message]
2023-03-08 12:35 ` Nick Alcock
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=20230308143137.GQ9667@google.com \
--to=lee@kernel.org \
--cc=hasegawa-hitomi@fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=nick.alcock@oracle.com \
--cc=tony@atomide.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: 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;
as well as URLs for NNTP newsgroup(s).