All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Markus Lidel <Markus.Lidel@shadowconnect.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] I2O: Lindent run and replacement of printk through osm printing functions
Date: Fri, 24 Jun 2005 19:34:02 -0400	[thread overview]
Message-ID: <42BC986A.4050807@pobox.com> (raw)
In-Reply-To: <42BC93EC.8030909@shadowconnect.com>

Markus Lidel wrote:
> Hello,
> 
> Jeff Garzik wrote:
> 
>> Linux Kernel Mailing List wrote:
>>
>>> tree da7e51e7204625f21371eac23a931f4fe479e9db
>>> parent 9e87545f06930c1d294423a8091d1077e7444a47
>>> author Markus Lidel <Markus.Lidel@shadowconnect.com> Fri, 24 Jun 2005 
>>> 12:02:23 -0700
>>> committer Linus Torvalds <torvalds@ppc970.osdl.org> Fri, 24 Jun 2005 
>>> 14:05:29 -0700
>>> [PATCH] I2O: Lindent run and replacement of printk through osm 
>>> printing functions
>>> Lindent run and replaced printk() through the corresponding osm_*() 
>>> function
>>
>> Please don't combine ANY code changes with an Lindent patch.
> 
> 
> Also if there is no functional change, only cosmetical (the osm_*() 
> function just mappes to printk(*, ...))?

Yes.  An Lindent patch needs to contain absolutely nothing else, not 
even documentation changes.

The rationale is that it is extremely difficult for reviewers to review 
your non-Lindent changes, because they are so obscured by Lindent.

In the past, one person even hid a [valid] security fix inside an 
Lindent patch.

	Jeff




  reply	other threads:[~2005-06-24 23:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200506241709.j5OH98vv000983@hera.kernel.org>
2005-06-24 22:26 ` [PATCH] I2O: Lindent run and replacement of printk through osm printing functions Jeff Garzik
2005-06-24 23:14   ` Markus Lidel
2005-06-24 23:34     ` Jeff Garzik [this message]
2005-06-26 17:57     ` Alan Cox

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=42BC986A.4050807@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=Markus.Lidel@shadowconnect.com \
    --cc=akpm@osdl.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 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.