From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Liviu Dudau <Liviu.Dudau@arm•com>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the mali-dp tree
Date: Tue, 15 Jan 2019 00:11:48 +1100 [thread overview]
Message-ID: <20190115001148.5963480c@canb.auug.org.au> (raw)
In-Reply-To: <20190114112916.GN20661@e110455-lin.cambridge.arm.com>
[-- Attachment #1: Type: text/plain, Size: 246 bytes --]
Hi Liviu,
On Mon, 14 Jan 2019 11:29:16 +0000 Liviu Dudau <Liviu.Dudau@arm•com> wrote:
>
> Sorry about that! I have now fixed those commits and also the build
> failure you were seeing.
Excellent, thanks.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-14 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 0:09 linux-next: Signed-off-by missing for commit in the mali-dp tree Stephen Rothwell
2019-01-14 11:29 ` Liviu Dudau
2019-01-14 13:11 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-06-08 6:13 Stephen Rothwell
2019-06-10 10:25 ` Liviu Dudau
2018-09-21 22:58 Stephen Rothwell
2018-09-24 1:01 ` Liviu Dudau
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=20190115001148.5963480c@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=Liviu.Dudau@arm$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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