All of lore.kernel.org
 help / color / mirror / Atom feed
From: ben@trinity.fluff.org (Ben Dooks)
To: linus-amlogic@lists.infradead.org
Subject: [PATCHv2] i2c: meson: allow build with COMPILE_TEST
Date: Wed, 6 Jul 2016 21:12:16 +0100	[thread overview]
Message-ID: <20160706201216.GA15529@trinity.fluff.org> (raw)
In-Reply-To: <20160706081340.GB1439@tetsubishi>

On Wed, Jul 06, 2016 at 05:13:41PM +0900, Wolfram Sang wrote:
> 
> > >> Signed-off-by: Ben Dooks <ben-linux@fluff.org>
> > >> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
> > > 
> > > Two signed-offs by you?
> > 
> > two different emails, got a patch written at home left in my work
> > tree so used both emails.
> 
> Please pick one so we know what you think if copyright belongs to you or
> your employer.

I thought I was being correct by having the From: matching the first
SoB, and the second being from the account I was sending it from

I will re-send from my personal laptop.

-- 
Ben Dooks, ben at fluff.org, http://www.fluff.org/ben/

Large Hadron Colada: A large Pina Colada that makes the universe disappear.

WARNING: multiple messages have this Message-ID (diff)
From: Ben Dooks <ben@trinity.fluff.org>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Ben Dooks <ben.dooks@codethink.co.uk>,
	linux-kernel@lists.codethink.co.uk,
	Ben Dooks <ben-linux@fluff.org>,
	linux-amlogic@lists.infradead.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCHv2] i2c: meson: allow build with COMPILE_TEST
Date: Wed, 6 Jul 2016 21:12:16 +0100	[thread overview]
Message-ID: <20160706201216.GA15529@trinity.fluff.org> (raw)
In-Reply-To: <20160706081340.GB1439@tetsubishi>

On Wed, Jul 06, 2016 at 05:13:41PM +0900, Wolfram Sang wrote:
> 
> > >> Signed-off-by: Ben Dooks <ben-linux@fluff.org>
> > >> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
> > > 
> > > Two signed-offs by you?
> > 
> > two different emails, got a patch written at home left in my work
> > tree so used both emails.
> 
> Please pick one so we know what you think if copyright belongs to you or
> your employer.

I thought I was being correct by having the From: matching the first
SoB, and the second being from the account I was sending it from

I will re-send from my personal laptop.

-- 
Ben Dooks, ben@fluff.org, http://www.fluff.org/ben/

Large Hadron Colada: A large Pina Colada that makes the universe disappear.

  reply	other threads:[~2016-07-06 20:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-05 18:19 [PATCH] i2c: meson: allow build with COMPILE_TEST Ben Dooks
2016-07-05 18:19 ` Ben Dooks
2016-07-05 18:24 ` [PATCHv2] " Ben Dooks
2016-07-05 18:24   ` Ben Dooks
2016-07-06  0:09   ` Wolfram Sang
2016-07-06  0:09     ` Wolfram Sang
2016-07-06  7:33     ` Ben Dooks
2016-07-06  7:33       ` Ben Dooks
2016-07-06  8:13       ` Wolfram Sang
2016-07-06  8:13         ` Wolfram Sang
2016-07-06 20:12         ` Ben Dooks [this message]
2016-07-06 20:12           ` Ben Dooks
2016-07-05 18:24 ` [PATCH] " Ben Dooks
2016-07-05 18:24   ` Ben Dooks

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=20160706201216.GA15529@trinity.fluff.org \
    --to=ben@trinity.fluff.org \
    --cc=linus-amlogic@lists.infradead.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.