All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Hurley <peter@hurleysoftware.com>
To: Denys Vlasenko <vda.linux@googlemail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Oleg Nesterov <oleg@redhat.com>,
	Greg KH <gregkh@linuxfoundation.org>
Subject: Re: Inline hunt results for 4.3.0-rc1
Date: Tue, 27 Oct 2015 11:31:26 -0400	[thread overview]
Message-ID: <562F98CE.4070200@hurleysoftware.com> (raw)
In-Reply-To: <CAK1hOcNPPVLkDBTvTxBmexPyGYJ5+H51D76JsROHmEoVipFfwQ@mail.gmail.com>

[ +cc Greg KH]

On 10/27/2015 10:32 AM, Denys Vlasenko wrote:
> Hi,
> 
> I have created a set of semi-automated scripts which look for
> large inlines in the kernel.
> 
> Recently I taught it to even generate "git format-patch" patches
> (unfortunately, only for inlines in *.c files, not *.h),
> and here are they for 4.3.0-rc1 - i.e. current Linus tree.
> 
> Submitting 300+ patches separately would amount to spamming,
> instead I encourage people to take a look at the patches
> on the Web:
> 
>     http://busybox.net/~vda/inline_hunt/4.3.0-rc1/

Looking over the drivers/tty/* patches, all of the patches
that save 300+ and 1000+ look ok to me, so if you want to
send those as a series (to the tty maintainers), I'll be
happy to mark them reviewed.

Wrt the "saves 100+' patches, some are ok, some are not,
and some I'd like to eliminate in a different way.
If you want to send those as a separate series, I could
mark as reviewed the ok patches, indicate which ones
to drop and which patches I'd be willing to rework.

Regards,
Peter Hurley



  parent reply	other threads:[~2015-10-27 15:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27 14:32 Inline hunt results for 4.3.0-rc1 Denys Vlasenko
2015-10-27 14:55 ` Hannes Frederic Sowa
2015-10-27 15:17   ` Denys Vlasenko
2015-10-27 15:25     ` Hannes Frederic Sowa
2015-10-27 15:31 ` Peter Hurley [this message]
2015-10-29  9:33 ` Denys Vlasenko

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=562F98CE.4070200@hurleysoftware.com \
    --to=peter@hurleysoftware.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=vda.linux@googlemail.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 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.