From: Liviu Dudau <Liviu.Dudau@arm•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
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: Mon, 10 Jun 2019 11:25:22 +0100 [thread overview]
Message-ID: <20190610102522.GE4173@e110455-lin.cambridge.arm.com> (raw)
In-Reply-To: <20190608161335.444f3d27@canb.auug.org.au>
On Sat, Jun 08, 2019 at 04:13:35PM +1000, Stephen Rothwell wrote:
> Hi Liviu,
Hi Stephen,
>
> Commits
>
> 74332e53e41d ("drm/komeda: Add image enhancement support")
> 108ddcf9238f ("drm/komeda: Add engine clock requirement check for the downscaling")
> e980ebbe5cee ("drm/komeda: Add writeback scaling support")
> 37bd61525f3a ("drm/komeda: Implement D71 scaler support")
> 50be77015da8 ("drm/komeda: Add the initial scaler support for CORE")
> 5bbab26c6a4a ("drm/komeda: Attach scaler to drm as private object")
> 0bb0d408280e ("drm/komeda: Potential error pointer dereference")
>
> are missing a Signed-off-by from their committer.
Sorry about that, I have now fixed them.
Best regards,
Liviu
>
> --
> Cheers,
> Stephen Rothwell
--
====================
| I would like to |
| fix the world, |
| but they're not |
| giving me the |
\ source code! /
---------------
¯\_(ツ)_/¯
next prev parent reply other threads:[~2019-06-10 10:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 6:13 linux-next: Signed-off-by missing for commit in the mali-dp tree Stephen Rothwell
2019-06-10 10:25 ` Liviu Dudau [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-14 0:09 Stephen Rothwell
2019-01-14 11:29 ` Liviu Dudau
2019-01-14 13:11 ` Stephen Rothwell
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=20190610102522.GE4173@e110455-lin.cambridge.arm.com \
--to=liviu.dudau@arm$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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