From: Mark Brown <broonie@kernel.org>
To: Anton Vorontsov <anton@enomsg.org>
Cc: "'Greg Kroah-Hartman'" <gregkh@linuxfoundation.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
Jingoo Han <jg1.han@samsung.com>,
"'David Woodhouse'" <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org, "'Joe Perches'" <joe@perches.com>,
"'Andrew Morton'" <akpm@linux-foundation.org>
Subject: Re: [PATCH 33/35] power: use dev_get_platdata()
Date: Thu, 29 Aug 2013 11:41:02 +0100 [thread overview]
Message-ID: <20130829104102.GS10783@sirena.org.uk> (raw)
In-Reply-To: <20130829030715.GA20317@teo>
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
On Wed, Aug 28, 2013 at 08:07:15PM -0700, Anton Vorontsov wrote:
> These changes not so much burden for me personally (it was actually easier
> for me to just apply the patch without all the arguing), but for those who
> actually do real bugfixes/features in the drivers: their local development
> trees will produce conflicts. Solving the trivial conflicts not a problem
> either, but irritating (especially realizing that you waste time resolving
> conflicts because of the "just cosmetic" crap).
> These days I don't code that much, but I was in that boat resolving
> "cosmetic" conflicts, and I did not like it. So I'm trying to solve the
> issue for drivers/power/ developers.
This sort of patche can be helpful when doing work over multiple drivers
- making the code more consistent means that it's much easier to pattern
match when looking over many different drivers.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-08-29 10:41 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
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 [this message]
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=20130829104102.GS10783@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anton@enomsg.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.