All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: pluhuxc@163.com, Samuel Martin <s.martin49@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package: add libtsm
Date: Wed, 28 Jul 2021 23:36:43 +0200	[thread overview]
Message-ID: <20210728233643.1f38f1b3@windsurf> (raw)
In-Reply-To: <c211cc8e-badf-5382-fc9f-f49edd247746@mind.be>

Hello,

On Wed, 2 Jun 2021 22:44:42 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:

>  I was going to apply to next, however:
> 
> On 06/04/2021 04:29, pluhuxc@163.com wrote:
> > From: luhui <pluhuxc@163.com>
> > 
> > Signed-off-by: luhui <pluhuxc@163.com>  
> 
>  We need a real name here. Signed-off-by is a legal statement, therefore it
> needs a real name. Itis a short way for you to  assert that you are entitled to
> contribute the patch under buildroot's  GPL license.  See
> http://elinux.org/Developer_Certificate_Of_Origin for more details.
> 
>  You can simply reply to this mail with the Signed-off-by and we will pick it up
> from there. Or feel free to resend the patch of course.
> 
>  Meanwhile, I'll already add my
> 
> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>

Unfortunately, there was never any reply to this patch, so I marked it
as Rejected.

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

      reply	other threads:[~2021-07-28 21:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-06  2:29 [Buildroot] [PATCH 1/1] package: add libtsm pluhuxc at 163.com
2021-06-02 20:44 ` Arnout Vandecappelle
2021-07-28 21:36   ` Thomas Petazzoni [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=20210728233643.1f38f1b3@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=arnout@mind.be \
    --cc=buildroot@buildroot.org \
    --cc=pluhuxc@163.com \
    --cc=s.martin49@gmail.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 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.