All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Vorontsov <anton@enomsg.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Jingoo Han <jg1.han@samsung.com>,
	"'David Woodhouse'" <dwmw2@infradead.org>,
	linux-kernel@vger.kernel.org, "'Joe Perches'" <joe@perches.com>,
	"'Greg Kroah-Hartman'" <gregkh@linuxfoundation.org>,
	"'Andrew Morton'" <akpm@linux-foundation.org>,
	"'Mark Brown'" <broonie@kernel.org>
Subject: Re: [PATCH 33/35] power: use dev_get_platdata()
Date: Wed, 28 Aug 2013 18:18:49 -0700	[thread overview]
Message-ID: <20130829011848.GA16891@teo> (raw)
In-Reply-To: <20130828083630.GF19256@mwanda>

On Wed, Aug 28, 2013 at 11:36:30AM +0300, Dan Carpenter wrote:
> He doesn't want to take the patch.  He's the maintainer so it's his
> choice.  That's the end of the story.

Just to clarify: I don't want to take the patch for a reason, not just
because of my mood today. Once the patch comes in combination with another
patch (or a plan) that actually makes use of the wrapper function, then
I'd happily apply/ack it.

This is the same story as global checkpatch.pl fixes: they are more harm
than good, and without the actual use of the dev_get_platdata(), the patch
falls into "global checkpatch.pl fixes" category.

Thanks,

Anton

  parent reply	other threads:[~2013-08-29  1:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30  8:19 [PATCH 33/35] power: use dev_get_platdata() Jingoo Han
2013-08-09 22:04 ` Anton Vorontsov
2013-08-12  0:22   ` Jingoo Han
2013-08-13  9:00     ` Dan Carpenter
2013-08-28  1:58       ` Anton Vorontsov
2013-08-28  2:19         ` Jingoo Han
2013-08-28  8:36           ` Dan Carpenter
2013-08-29  0:25             ` Jingoo Han
2013-08-29  1:18             ` Anton Vorontsov [this message]
2013-08-29  2:07               ` 'Greg Kroah-Hartman'
2013-08-29  2:18                 ` Jingoo Han
2013-08-29  3:07                 ` Anton Vorontsov
2013-08-29 10:41                   ` Mark Brown
2013-08-29  2:14               ` Jingoo Han

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=20130829011848.GA16891@teo \
    --to=anton@enomsg.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=dan.carpenter@oracle.com \
    --cc=dwmw2@infradead.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jg1.han@samsung.com \
    --cc=joe@perches.com \
    --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.