From: Mark Brown <broonie@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Mike Frysinger <vapier@gentoo.org>,
"uclinux-dist-devel@blackfin.uclinux.org"
<uclinux-dist-devel@blackfin.uclinux.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] blackfin: bf533-stamp: Remove bogus "||"
Date: Sat, 1 Jun 2013 23:06:27 +0100 [thread overview]
Message-ID: <20130601220627.GW16790@sirena.org.uk> (raw)
In-Reply-To: <CAMuHMdWN6Ur47fBu3oZpah4fTaV+mV4Y_Q=SvV_jet-3FiZEUQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 684 bytes --]
On Sat, Jun 01, 2013 at 11:29:23PM +0200, Geert Uytterhoeven wrote:
> On Sat, Jun 1, 2013 at 11:10 PM, Mark Brown <broonie@kernel.org> wrote:
> >> Sorry, I sent it to your Wolfson address, as suggested by get_maintainter.pl:
> >> Mark Brown <broonie@opensource.wolfsonmicro.com> (commit_signer:3/4=75%)
> > You're not using a current version of the tree you're submitting
> > against (which you should always do)...
> I'm using next-20130531.
Which has broonie@kernel.org listed as the maintainer address... the
commit signer information isn't awfully reliable at the best of times,
it's got a big tendency to throw up false positives for things like
people doing cleanup work.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-06-01 22:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 9:40 [PATCH -next] blackfin: bf533-stamp: Remove bogus "||" Geert Uytterhoeven
2013-05-31 11:37 ` Lars-Peter Clausen
2013-05-31 11:40 ` Lars-Peter Clausen
2013-06-01 19:03 ` Mark Brown
2013-06-01 20:48 ` Geert Uytterhoeven
2013-06-01 21:10 ` Mark Brown
2013-06-01 21:29 ` Geert Uytterhoeven
2013-06-01 22:06 ` Mark Brown [this message]
2013-06-02 8:04 ` Geert Uytterhoeven
2013-06-02 10:33 ` Mark Brown
2013-05-31 18:33 ` Mike Frysinger
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=20130601220627.GW16790@sirena.org.uk \
--to=broonie@kernel.org \
--cc=geert@linux-m68k.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.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