From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH] ASoC: atmel_ssc_dai: distinguish the different SSC
Date: Wed, 2 Mar 2016 19:33:05 +0900 [thread overview]
Message-ID: <20160302103304.GF18327@sirena.org.uk> (raw)
In-Reply-To: <56D6AC37.8080302@atmel.com>
On Wed, Mar 02, 2016 at 10:02:47AM +0100, Nicolas Ferre wrote:
> Le 02/03/2016 02:04, Mark Brown a ?crit :
> > On Tue, Mar 01, 2016 at 10:54:29AM +0100, Nicolas Ferre wrote:
> >> Signed-off-by: Songjun Wu <songjun.wu@atmel.com>
> >> Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> > I can't look at patches that aren't signed off, please see
> > SubmittingPatches for details.
> Songjun did sign the patch, I'm puzzled...
> Ah, you mean that I should have signed it myself as well as I am the
> actual sender... ok, as it's a "resend" like the subject says and that
> the first patch was actually sent by Songjun, I though it would be legit.
> Anyway, I'll resend it with my own Signed tag.
Yes, if you are posting a patch you need to include your signoff -
please see SubmittingPatches for details.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160302/de04b8fa/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: linux-arm-kernel@lists.infradead.org,
Songjun Wu <songjun.wu@atmel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, tiwai@suse.com
Subject: Re: [RESEND PATCH] ASoC: atmel_ssc_dai: distinguish the different SSC
Date: Wed, 2 Mar 2016 19:33:05 +0900 [thread overview]
Message-ID: <20160302103304.GF18327@sirena.org.uk> (raw)
In-Reply-To: <56D6AC37.8080302@atmel.com>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
On Wed, Mar 02, 2016 at 10:02:47AM +0100, Nicolas Ferre wrote:
> Le 02/03/2016 02:04, Mark Brown a écrit :
> > On Tue, Mar 01, 2016 at 10:54:29AM +0100, Nicolas Ferre wrote:
> >> Signed-off-by: Songjun Wu <songjun.wu@atmel.com>
> >> Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> > I can't look at patches that aren't signed off, please see
> > SubmittingPatches for details.
> Songjun did sign the patch, I'm puzzled...
> Ah, you mean that I should have signed it myself as well as I am the
> actual sender... ok, as it's a "resend" like the subject says and that
> the first patch was actually sent by Songjun, I though it would be legit.
> Anyway, I'll resend it with my own Signed tag.
Yes, if you are posting a patch you need to include your signoff -
please see SubmittingPatches for details.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-03-02 10:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 9:54 [RESEND PATCH] ASoC: atmel_ssc_dai: distinguish the different SSC Nicolas Ferre
2016-03-01 9:54 ` Nicolas Ferre
2016-03-02 1:04 ` Mark Brown
2016-03-02 1:04 ` Mark Brown
2016-03-02 9:02 ` Nicolas Ferre
2016-03-02 9:02 ` Nicolas Ferre
2016-03-02 10:33 ` Mark Brown [this message]
2016-03-02 10:33 ` 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=20160302103304.GF18327@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-arm-kernel@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.