linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: shuah <shuah@kernel.org>
To: "Daniel Díaz" <daniel.diaz@linaro.org>
Cc: Fathi Boudra <fathi.boudra@linaro.org>,
	Denys Dmytriyenko <denys@ti.com>,
	"open list:KERNEL SELFTEST FRAMEWORK" 
	<linux-kselftest@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	shuah <shuah@kernel.org>
Subject: Re: [PATCH 1/4] selftests: lib: allow to override CC in the top-level Makefile
Date: Mon, 28 Jan 2019 08:01:15 -0700	[thread overview]
Message-ID: <a68c3fdd-081a-74ea-8d98-30eaf3d70446@kernel.org> (raw)
In-Reply-To: <CAEUSe7_eYmMSovO4JAabh+83CtY2L8eeMoCVKKS5P-fs7zVhjg@mail.gmail.com>

Hi Daniel,

On 1/18/19 10:54 AM, Daniel Díaz wrote:
> Hello!
> 
> On Wed, 16 Jan 2019 at 15:56, shuah <shuah@kernel.org> wrote:
>>
>> On 1/16/19 10:43 AM, Daniel Díaz wrote:
>>> From: Fathi Boudra <fathi.boudra@linaro.org>
>>>
>>> Relax CC assignment to allow to override CC in the top-level Makefile.
>>>
>>> Signed-off-by: Denys Dmytriyenko <denys@ti.com>

Author signed-off missing on this patch. I am dropping this patch
from rc5 for now. Please fix it resend the patch. In the future,
I would like to see that author sends the patch.

thanks,
-- Shuah


  reply	other threads:[~2019-01-28 15:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 17:43 [PATCH 1/4] selftests: lib: allow to override CC in the top-level Makefile Daniel Díaz
2019-01-16 17:43 ` [PATCH 2/4] selftests: net: use LDLIBS instead of LDFLAGS Daniel Díaz
2019-01-16 17:43 ` [PATCH 3/4] selftests: seccomp: " Daniel Díaz
2019-01-16 18:13   ` Kees Cook
2019-01-16 18:26     ` shuah
2019-01-16 17:43 ` [PATCH 4/4] selftests: timers: " Daniel Díaz
2019-01-16 21:56 ` [PATCH 1/4] selftests: lib: allow to override CC in the top-level Makefile shuah
2019-01-18 17:54   ` Daniel Díaz
2019-01-28 15:01     ` shuah [this message]
2019-01-28 15:42       ` Denys Dmytriyenko
2019-01-28 16:28         ` shuah
2019-01-28 17:01           ` Daniel Díaz

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=a68c3fdd-081a-74ea-8d98-30eaf3d70446@kernel.org \
    --to=shuah@kernel.org \
    --cc=daniel.diaz@linaro.org \
    --cc=denys@ti.com \
    --cc=fathi.boudra@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).