All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Emese Revfy <re.emese@gmail.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
	Paul Mundt <lethal@linux-sh.org>, Matthew Wilcox <matthew@wil.cx>,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	viro@zeniv.linux.org.uk, akpm@linux-foundation.org,
	Greg KH <gregkh@suse.de>
Subject: Re: [PATCH 0/1] Constify struct address_space_operations for 2.6.32-git-053fe57ac v2
Date: Tue, 15 Dec 2009 11:47:06 +0100	[thread overview]
Message-ID: <20091215104706.GG17930@elf.ucw.cz> (raw)
In-Reply-To: <4B26C68D.1080300@gmail.com>

On Tue 2009-12-15 00:13:17, Emese Revfy wrote:
> Arjan van de Ven wrote:
> > Now, a 300 patch series to lkml is not the way to do this.
> > First step is to make checkpatch.pl warn about new cases.
> 
> I will add this structures the checkpatch in the next patch series.
> 
> > Second step should be to convert all definitions, but using the "one
> > patch per maintainer" rule, not "one patch per file" rule. Yes it's
> > somewhat janitorial, but no it's not a big deal as long as it's not 300
> > patches to lkml. And it is much better than whitespace changes; it's
> > a real quality improvement to the kernel (in terms of code generation
> > and API)
> 
> The first series was based on one patch per structure type, the current
> split-up is based on one patch per structure type *and* subsystem as
> suggested by Greg KH. I used get_maintainer --subsystem to find them which
> resulted in 150 patches. If you know a better way or want per-type patches,
> please let me know (and discuss it with Greg ;).

Please push VFS patches first -- in small series. Unless you can
address Al Viro's objections, I do not think rest should go in (and no
need to spam l-k in the process).
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2009-12-15 10:47 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-13 23:58 [PATCH 00/22] Constify struct backlight_ops for 2.6.32-git-053fe57ac v2 re.emese
2009-12-13 23:58 ` [PATCH 01/22] " re.emese
2009-12-13 23:58 ` [PATCH 02/22] " re.emese
2009-12-13 23:58 ` [PATCH 03/22] " re.emese
2009-12-13 23:58 ` [PATCH 04/22] " re.emese
2009-12-13 23:58 ` [PATCH 05/22] " re.emese
2009-12-15 22:47   ` Richard Purdie
2009-12-16 22:39     ` Emese Revfy
2009-12-13 23:58 ` [PATCH 06/22] " re.emese
2009-12-13 23:58 ` [PATCH 1/3] Constify struct acpi_dock_ops " re.emese
2009-12-13 23:58 ` [PATCH 07/22] Constify struct backlight_ops " re.emese
2009-12-13 23:59 ` [PATCH 2/3] Constify struct acpi_dock_ops " re.emese
2009-12-13 23:59 ` [PATCH 08/22] Constify struct backlight_ops " re.emese
2009-12-13 23:59 ` [PATCH 09/22] " re.emese
2009-12-13 23:59 ` [PATCH 3/3] Constify struct acpi_dock_ops " re.emese
2009-12-13 23:59 ` [PATCH 10/22] Constify struct backlight_ops " re.emese
2009-12-14  0:27   ` Jonathan Woithe
2009-12-13 23:59 ` [PATCH 11/22] " re.emese
2009-12-13 23:59 ` [PATCH 12/22] " re.emese
2009-12-13 23:59 ` [PATCH 13/22] " re.emese
2009-12-13 23:59 ` [PATCH 14/22] " re.emese
2009-12-13 23:59 ` [PATCH 15/22] " re.emese
2009-12-13 23:59 ` [PATCH 16/22] " re.emese
2009-12-13 23:59 ` [PATCH 1/1] Constify struct address_space_operations " re.emese
2009-12-13 23:59 ` [PATCH 17/22] Constify struct backlight_ops " re.emese
2009-12-13 23:59 ` [PATCH 18/22] " re.emese
2009-12-13 23:59 ` [PATCH 19/22] " re.emese
2009-12-13 23:59 ` [PATCH 20/22] " re.emese
2009-12-13 23:59 ` [PATCH 21/22] " re.emese
2009-12-13 23:59 ` [PATCH 22/22] " re.emese
2009-12-14  0:38 ` [PATCH 0/1] Constify struct address_space_operations " Matthew Wilcox
2009-12-14  1:33   ` Emese Revfy
2009-12-14  2:19     ` Paul Mundt
2009-12-14  7:08       ` Emese Revfy
2009-12-14 11:26         ` Pavel Machek
2009-12-14 16:00           ` Arjan van de Ven
2009-12-14 16:30             ` Matthew Wilcox
2009-12-14 21:25             ` Pavel Machek
2009-12-14 22:17               ` Arjan van de Ven
2009-12-14 22:21                 ` Pavel Machek
2009-12-14 22:41                 ` Emese Revfy
2009-12-15 18:14                   ` Pavel Machek
2009-12-15 23:28                     ` Emese Revfy
2009-12-16  0:04                       ` Al Viro
2009-12-16  8:06                       ` Pavel Machek
2009-12-16 22:24                         ` Emese Revfy
2009-12-14 23:13             ` Emese Revfy
2009-12-15 10:47               ` Pavel Machek [this message]
2009-12-15 19:12             ` Al Viro
2009-12-14 12:36         ` Paul Mundt
2009-12-14 22:20           ` Emese Revfy
2009-12-15  0:01             ` Arjan van de Ven
2009-12-15 23:53               ` Emese Revfy
2009-12-14 11:18     ` Pavel Machek

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=20091215104706.GG17930@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=gregkh@suse.de \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=re.emese@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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.