From: Mark Brown <broonie@kernel.org>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: arm-soc <arm@kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
Ryder Lee <ryder.lee@mediatek.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Sean Wang <sean.wang@mediatek.com>
Subject: Re: [GIT PULL] ARM: mediatek: soc driver updates for v4.18
Date: Fri, 18 May 2018 16:13:10 +0100 [thread overview]
Message-ID: <20180518151310.GG24209@sirena.org.uk> (raw)
In-Reply-To: <3e416f8f-b038-9bfe-7038-98aec5224620@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 881 bytes --]
On Fri, May 18, 2018 at 05:11:32PM +0200, Matthias Brugger wrote:
> On 17/05/18 06:46, Mark Brown wrote:
> > On Mon, May 14, 2018 at 01:32:49PM +0200, Matthias Brugger wrote:
> > > ----------------------------------------------------------------
> > > Matthias Brugger (1):
> > > Merge commit 'f15cd6d99198e9c15229aefec639a34a6e8174c6' into
> > > v.4.17-next/soc-test
> > There is a signed tag for this - please don't ever pull anything from me
> > without a signed tag, while I try to avoid rewriting history it does
> > sometimes happen but if I've made a signed tag part of that is me saying
> > I know other people might've merged the commit.
> You are right I got confused about this.
> Anrd, Olof do you want me to resubmit?
I'm OK with leaving things as is - that was more a request for the
future than a request to rewrite history (if it's already been merged).
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2018-05-18 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 11:32 [GIT PULL] ARM: mediatek: soc driver updates for v4.18 Matthias Brugger
[not found] ` <bd033549-4998-e376-eb92-16111ec71a07-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-05-15 20:43 ` Olof Johansson
2018-05-17 4:46 ` Mark Brown
[not found] ` <20180517044600.GC20254-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2018-05-18 15:11 ` Matthias Brugger
2018-05-18 15:13 ` 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=20180518151310.GG24209@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.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