From: "Sachin Saxena (OSS)" <sachin.saxena@oss.nxp.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, Akhil Goyal <akhil.goyal@nxp.com>,
Gagandeep Singh <g.singh@nxp.com>,
ferruh.yigit@intel.com
Subject: Re: [dpdk-dev] [PATCH v1] maintainers: update for nxp bus, dpaa, dpaa2 and enetc
Date: Thu, 24 Sep 2020 07:23:07 +0530 [thread overview]
Message-ID: <bdd58419-0e52-f544-370e-29265a2f3204@oss.nxp.com> (raw)
In-Reply-To: <3285200.5Z1SrQoqOM@thomas>
On 24-Sep-20 5:29 AM, Thomas Monjalon wrote:
> 14/09/2020 16:06, Sachin Saxena (OSS):
>> From: Sachin Saxena <sachin.saxena@oss.nxp.com>
>>
>> Updated email of maintainer.
>>
>> Signed-off-by: Sachin Saxena <sachin.saxena@oss.nxp.com>
>> ---
>> NXP buses
>> M: Hemant Agrawal <hemant.agrawal@nxp.com>
>> -M: Sachin Saxena <sachin.saxena@nxp.com>
>> +M: Sachin Saxena <sachin.saxena@oss.nxp.com>
> Tab is replaced with a space,
> and applied, thanks.
Thanks Thomas.
Just FYI.. I was getting following checkpatch Warning when I used space
instead of tab. To avoid this warning I submitted the patch with tab.
WARNING: MAINTAINERS entries use one tab after TYPE:
#19: FILE: MAINTAINERS:805:
+M: Sachin Saxena <sachin.saxena@oss.nxp.com>
> Sachin, please could you help migrating NXP drivers to the new close behaviour?
> It is really urgent now:
> http://inbox.dpdk.org/dev/80837131.n3tlCtGQ32@thomas/
> http://inbox.dpdk.org/dev/20200913220711.3768597-17-thomas@monjalon.net/
>
Sure.
prev parent reply other threads:[~2020-09-24 1:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 14:06 Sachin Saxena (OSS)
2020-09-23 23:59 ` Thomas Monjalon
2020-09-24 1:53 ` Sachin Saxena (OSS) [this message]
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=bdd58419-0e52-f544-370e-29265a2f3204@oss.nxp.com \
--to=sachin.saxena@oss.nxp.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=g.singh@nxp.com \
--cc=thomas@monjalon.net \
/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).