linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Łukasz Stelmach" <l.stelmach@samsung.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Joe Perches <joe@perches.com>,
	linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Subject: Re: Bad MAINTAINERS pattern in section 'SAMSUNG EXYNOS TRUE RANDOM NUMBER GENERATOR (TRNG) DRIVER'
Date: Mon, 01 Oct 2018 10:07:37 +0200	[thread overview]
Message-ID: <875zym5bue.fsf%l.stelmach@samsung.com> (raw)
In-Reply-To: <20180928220330.31325-1-joe@perches.com>

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

It was <2018-09-29 sob 00:03>, when Joe Perches wrote:
> Please fix this defect appropriately.
>
> linux-next MAINTAINERS section:
>
> 	12851	SAMSUNG EXYNOS TRUE RANDOM NUMBER GENERATOR (TRNG) DRIVER
> 	12852	M:	Łukasz Stelmach <l.stelmach@samsung.com>
> 	12853	L:	linux-samsung-soc@vger.kernel.org
> 	12854	S:	Maintained
> 	12855	F:	drivers/char/hw_random/exynos-trng.c
> -->	12856	F:	Documentation/devicetree/bindings/rng/samsung,exynos5250-trng.txt
>
> Commit that introduced this:
>
> commit 6cd225cc5d8a6526b2bea41955882be55d4f109e
>  Author: Łukasz Stelmach <l.stelmach@samsung.com>
>  Date:   Fri Dec 22 17:48:35 2017 +0100
>  
>      hwrng: exynos - add Samsung Exynos True RNG driver
>      
>      Add support for True Random Number Generator found in Samsung Exynos
>      5250+ SoCs.
>      
>      Signed-off-by: Łukasz Stelmach <l.stelmach@samsung.com>
>      Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
>      Acked-by: Philippe Ombredanne <pombredanne@nexb.com>
>      Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
>  
>   MAINTAINERS                          |   7 ++
>   drivers/char/hw_random/Kconfig       |  12 ++
>   drivers/char/hw_random/Makefile      |   1 +
>   drivers/char/hw_random/exynos-trng.c | 237 +++++++++++++++++++++++++++++++++++
>   4 files changed, 257 insertions(+)
>
> No commit with Documentation/devicetree/bindings/rng/samsung,exynos5250-trng.txt found

Please merge the version 3[1] of the patch you've acked[2].

[1] https://www.spinics.net/lists/linux-samsung-soc/msg61372.html
[2] https://www.spinics.net/lists/linux-samsung-soc/msg61272.html
-- 
Łukasz Stelmach
Samsung R&D Institute Poland
Samsung Electronics

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2018-10-01  8:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-28 22:03 Bad MAINTAINERS pattern in section 'SAMSUNG EXYNOS TRUE RANDOM NUMBER GENERATOR (TRNG) DRIVER' Joe Perches
     [not found] ` <CGME20181001080750epcas2p21b4c3e14be32859f31bede0656ffa09d@epcas2p2.samsung.com>
2018-10-01  8:07   ` Łukasz Stelmach [this message]
2018-10-01 12:47     ` Rob Herring
     [not found]       ` <CGME20181002075700epcas2p1e1650ae02c1d6b1bfb946b146d4ce223@epcas2p1.samsung.com>
2018-10-02  7:56         ` [PATCH] dt-bindings: hwrng: Add Samsung Exynos 5250+ True RNG bindings Łukasz Stelmach
2018-10-02 11:14           ` Krzysztof Kozlowski
     [not found]           ` <CGME20181004074641epcas1p287225c19a28c713327725d089068f960@epcas1p2.samsung.com>
2018-10-04  7:45             ` [PATCH v5.1] " Łukasz Stelmach

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=875zym5bue.fsf%l.stelmach@samsung.com \
    --to=l.stelmach@samsung.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=robh+dt@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).