public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: Philippe Ombredanne <pombredanne@nexb.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	Linux MIPS <linux-mips@linux-mips.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Huacai Chen <chenhc@lemote.com>
Subject: Re: [PATCHv2 1/8] MIPS: Loongson64: cleanup all cs5536 files to use SPDX Identifier
Date: Sun, 31 Dec 2017 21:14:23 +0800	[thread overview]
Message-ID: <1514726063.1668.7.camel@flygoat.com> (raw)
In-Reply-To: <CAOFm3uFM+7n_YaKBkZV6jV4VHCBhtGhUTLbB4uedMaCa+nf3PA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 540 bytes --]

On 2017-12-31 Sun 12:17 +0100,Philippe Ombredanne wrote:
> Did you CC the original authors? You would need their signoff or at
> least an ack IMHO

Yeah, I CC Huacai Chen in v1 as the Lemote staff who in charge of
Loongson's mainline kernel. Can he sign-off for all the original
authors who were from ICT and Lemote?
As far as I know, some authors are no longer working in Lemote. And I
can't see their new email addresses so it may hard to get their ack or
sign-off.
Thanks for your adivce.

--
Best Regards
Jiaxun Yang

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-12-31 13:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-26 13:23 Cleanup loongson64 mach to use SPDX copyright format Jiaxun Yang
2017-12-26 13:23 ` [PATCH 1/7] MIPS: Loongson64: cleanup all cs5536 files to use SPDX Identifier Jiaxun Yang
2017-12-29 12:40   ` Philippe Ombredanne
2017-12-26 13:23 ` [PATCH 2/7] MIPS: Loongson64: cleanup all loongson common " Jiaxun Yang
2017-12-26 13:23 ` [PATCH 3/7] MIPS: Loongson64: cleanup all fuloong-2e " Jiaxun Yang
2017-12-26 13:23 ` [PATCH 4/7] MIPS: Loongson64: cleanup all lemote-2f " Jiaxun Yang
2017-12-26 13:23 ` [PATCH 5/7] MIPS: Loongson64: cleanup all loongson-3 " Jiaxun Yang
2017-12-26 13:23 ` [PATCH 6/7] MIPS: Loongson64: cleanup all mach " Jiaxun Yang
2017-12-26 13:23 ` [PATCH 7/7] MIPS: Loongson64: cleanup all include " Jiaxun Yang
2017-12-30 18:28 ` Cleanup loongson64 mach to use SPDX copyright format v2 Jiaxun Yang
2017-12-30 18:28   ` [PATCHv2 1/8] MIPS: Loongson64: cleanup all cs5536 files to use SPDX Identifier Jiaxun Yang
2017-12-31 11:17     ` Philippe Ombredanne
2017-12-31 13:14       ` Jiaxun Yang [this message]
2017-12-31 13:54         ` Philippe Ombredanne
2018-01-02  2:32           ` Huacai Chen
2018-02-20 23:06     ` James Hogan
2017-12-30 18:28   ` [PATCHv2 2/8] MIPS: Loongson64: cleanup all loongson common " Jiaxun Yang
2017-12-30 18:28   ` [PATCHv2 3/8] MIPS: Loongson64: cleanup all fuloong-2e " Jiaxun Yang
2017-12-30 18:28   ` [PATCHv2 4/8] MIPS: Loongson64: cleanup all lemote-2f " Jiaxun Yang
2017-12-30 18:28   ` [PATCHv2 5/8] MIPS: Loongson64: cleanup all loongson-3 " Jiaxun Yang
2017-12-30 18:28   ` [PATCHv2 6/8] MIPS: Loongson64: cleanup all mach " Jiaxun Yang
2018-02-20 23:01     ` James Hogan
2017-12-30 18:28   ` [PATCHv2 7/8] MIPS: Loongson64: cleanup all include " Jiaxun Yang

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=1514726063.1668.7.camel@flygoat.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=chenhc@lemote.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=pombredanne@nexb.com \
    --cc=ralf@linux-mips.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