From: Lee Jones <lee.jones@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Javier Martinez Canillas <javier@dowhile0.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] MAINTAINERS: Update MAX77802 PMIC entry
Date: Tue, 16 May 2017 08:51:40 +0100 [thread overview]
Message-ID: <20170516075140.vsw3el5r7d2krylb@dell> (raw)
In-Reply-To: <20170514095216.3wterzz6swowpzli@sirena.org.uk>
On Sun, 14 May 2017, Mark Brown wrote:
> On Thu, May 04, 2017 at 12:36:25AM -0400, Javier Martinez Canillas wrote:
>
> > Acked-by: Mark Brown <broonie@kernel.org>
>
> Since I'm expected to apply this I wouldn't normally expect to see my
> ack - like I say if I'm acking something for me it's normally because I
> expect someone else to actually apply it (that's the standard thing).
I don't agree with this. You provided your Ack under the assumption
that it would be applied though another tree, but there is no reason
why it would be dropped just because that is no longer the case.
It's commonplace for me to provide Acks for patches I know will
*eventually* be applied by me. Removing them when applying patches is
part of my daily routine.
TL;DR: If a Maintainer (or anyone for that matter) provides a *-by
tag, it should be carried forward with the (unchanged) patch until
acceptance.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2017-05-16 7:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 4:36 Javier Martinez Canillas
2017-05-14 9:52 ` Mark Brown
2017-05-16 7:51 ` Lee Jones [this message]
2017-05-16 11:06 ` Mark Brown
2017-05-16 11:56 ` Javier Martinez Canillas
2017-05-22 11:06 ` Lee Jones
2017-05-22 12:06 ` Mark Brown
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=20170516075140.vsw3el5r7d2krylb@dell \
--to=lee.jones@linaro.org \
--cc=broonie@kernel.org \
--cc=javier@dowhile0.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®