From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM:omap2: using strlcpy instead of strncpy
Date: Sat, 2 Feb 2013 10:07:24 -0800 [thread overview]
Message-ID: <20130202180723.GB577@atomide.com> (raw)
In-Reply-To: <510C7925.9040006@asianux.com>
* Chen Gang <gang.chen@asianux.com> [130201 18:29]:
> ? 2013?02?02? 06:45, Tony Lindgren ??:
> > Added Peter to cc on this one too, it's best that he queues
> > all the twl changes.
>
> is it suitable to sync the MAINTAINER file for it ?
> if suitable, can you help to change it ?
Yes I suggest we add Peter as the maintainer for all twl
related things.
Regards,
Tony
next prev parent reply other threads:[~2013-02-02 18:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 11:46 [PATCH] ARM:omap2: using strlcpy instead of strncpy Chen Gang
2013-02-01 22:45 ` Tony Lindgren
2013-02-02 2:25 ` Chen Gang
2013-02-02 18:07 ` Tony Lindgren [this message]
2013-02-04 1:17 ` Chen Gang
2013-02-04 9:00 ` Peter Ujfalusi
2013-02-04 18:18 ` Tony Lindgren
2013-02-05 2:18 ` Chen Gang
2013-02-05 18:56 ` Tony Lindgren
2013-02-06 2:05 ` Chen Gang
2013-02-04 8:54 ` Peter Ujfalusi
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=20130202180723.GB577@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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).