public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] arm: exynos: arndale: Replace Chander Kashyap inactive maintainer
Date: Fri, 22 Feb 2019 22:39:36 +0100	[thread overview]
Message-ID: <20190222223936.09ee89b5@jawa> (raw)
In-Reply-To: <20190222183643.5995-1-krzk@kernel.org>

On Fri, 22 Feb 2019 19:36:40 +0100
Krzysztof Kozlowski <krzk@kernel.org> wrote:

> Last activity from Arndale (Exynos5250) board maintainer Chander
> Kashyap was in January 2014 (Signed-off).  Recently his samsung.com
> email bounces with 550 (5.1.1 Recipient address rejected: User
> unknown).
> 
> Add Krzysztof Kozlowski as odd fixer for this board.
> 
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> 
> ---
> 
> Although I do not have this particular board, but still I can try to
> take care about odd fixes.  Instead I have few other boards based on
> Exynos4412 (Odroids) and 542x (Arndale Octa, Odroids).  I also run
> automated Linux kernel boot tests for my boards and I maintain the
> Samsung SoCs in Linux kernel.
> ---
>  board/samsung/arndale/MAINTAINERS | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/board/samsung/arndale/MAINTAINERS
> b/board/samsung/arndale/MAINTAINERS index 7dc17854d1b3..98ccaa42a86e
> 100644 --- a/board/samsung/arndale/MAINTAINERS
> +++ b/board/samsung/arndale/MAINTAINERS
> @@ -1,6 +1,6 @@
>  ARNDALE BOARD
> -M:	Chander Kashyap <k.chander@samsung.com>
> -S:	Maintained
> +M:	Krzysztof Kozlowski <krzk@kernel.org>
> +S:	Odd Fixes
>  F:	board/samsung/arndale/
>  F:	include/configs/arndale.h
>  F:	configs/arndale_defconfig

(Fully) Acked-by: Lukasz Majewski <lukma@denx.de>


Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190222/c91c78e0/attachment.sig>

  parent reply	other threads:[~2019-02-22 21:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20190222183701epcas3p2338ba674d08d139e5941ec02c9e84556@epcas3p2.samsung.com>
2019-02-22 18:36 ` [U-Boot] [PATCH 1/4] arm: exynos: arndale: Replace Chander Kashyap inactive maintainer Krzysztof Kozlowski
2019-02-22 18:36   ` [U-Boot] [PATCH 2/4] configs: odroid_xu3: Use consistent syntax for #include Krzysztof Kozlowski
2019-02-24 21:32     ` Lukasz Majewski
2019-03-12  1:10     ` Minkyu Kang
2019-02-22 18:36   ` [U-Boot] [PATCH 3/4] configs: odroid_xu3: Unify indentation Krzysztof Kozlowski
2019-02-24 21:32     ` Lukasz Majewski
2019-03-12  1:10     ` Minkyu Kang
2019-02-22 18:36   ` [U-Boot] [PATCH 4/4] arm: exynos: Remove duplicated "boardname" env setting Krzysztof Kozlowski
2019-02-24 21:32     ` Lukasz Majewski
2019-03-12  1:10     ` Minkyu Kang
2019-02-22 21:39   ` Lukasz Majewski [this message]
2019-03-12  1:10   ` [U-Boot] [PATCH 1/4] arm: exynos: arndale: Replace Chander Kashyap inactive maintainer Minkyu Kang

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=20190222223936.09ee89b5@jawa \
    --to=lukma@denx.de \
    --cc=u-boot@lists.denx.de \
    /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