From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Axel Lin <axel.lin@ingics.com>,
Bengt Jonsson <bengt.g.jonsson@stericsson.com>,
Mattias WALLIN <mattias.wallin@stericsson.com>,
Emeric Vigier <emeric.vigier@stericsson.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFT][PATCH 1/2] regulator: ab8500: Fix build error
Date: Tue, 19 Feb 2013 12:04:04 +0000 [thread overview]
Message-ID: <20130219120404.GA23508@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20130218102421.GA3538@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 923 bytes --]
On Mon, Feb 18, 2013 at 10:24:21AM +0000, Lee Jones wrote:
> The patches which caused the issues addressed by this patch-set have
> since been rewritten. I have subsequently requested that Mark deletes
> the AB8500 for-next branch. We're going to start again after this
> merge window.
So, as discussed you really shouldn't have done that - unless there's a
very serious problem you should be assuming that patches that have been
applied are going to stay applied and working from the latest upstream
tree. Once something is in -next the expectation is that it's going to
be sent during the next merge window. As well as the issues with
maintainers getting fed up having to look at the same code over and over
again it causes people like Axel to waste their time.
However I am probably going to just throw away the current ab8500 work
this time. Please resend your patches after the merge window (which
just opened).
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-02-19 12:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 2:57 [RFT][PATCH 1/2] regulator: ab8500: Fix build error Axel Lin
2013-02-18 2:59 ` [RFT][PATCH 2/2] regulator: ab8500: Use regulator_list_voltage_linear for fixed voltage Axel Lin
2013-02-18 3:24 ` [RFT][PATCH] regulator: ab8500: Remove get_voltage_sel " Axel Lin
2013-02-18 10:24 ` [RFT][PATCH 1/2] regulator: ab8500: Fix build error Lee Jones
2013-02-19 12:04 ` Mark Brown [this message]
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=20130219120404.GA23508@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=axel.lin@ingics.com \
--cc=bengt.g.jonsson@stericsson.com \
--cc=emeric.vigier@stericsson.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mattias.wallin@stericsson.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).