From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Anand Ashok Dumbre <ANANDASH@xilinx.com>,
linux-kernel@vger.kernel.org, jic23@kernel.org, lars@metafoo.de,
linux-iio@vger.kernel.org, git <git@xilinx.com>,
Michal Simek <michals@xilinx.com>,
gregkh@linuxfoundation.org, rafael@kernel.org,
linux-acpi@vger.kernel.org, heikki.krogerus@linux.intel.com
Subject: Re: [PATCH v9 5/5] MAINTAINERS: Add maintainer for xilinx-ams
Date: Wed, 17 Nov 2021 21:28:53 +0200 [thread overview]
Message-ID: <YZVX9R/TMvkPwuuF@smile.fi.intel.com> (raw)
In-Reply-To: <164612d20b252a28dda74f5058e0aacb@perches.com>
On Wed, Nov 17, 2021 at 10:46:20AM -0800, Joe Perches wrote:
> On 2021-11-17 09:08, Andy Shevchenko wrote:
> > On Wed, Nov 17, 2021 at 6:05 PM Joe Perches <joe@perches.com> wrote:
>
> > > What do you think checkpatch is supposed to find?
>
> > To me AMS should precede AXI and not the other way around. Agree?
>
> Sure but checkpatch just looks at patches and doesn't inspect the patched
> file, apply the patch then look at the result. The patch itself looks fine.
I see, checkpatch simply doesn't have such functionality and maintainers should
ask people to rung parse-maintainers.pl from time to time…
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-11-17 19:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 15:08 [PATCH v9 0/5] Add Xilinx AMS Driver Anand Ashok Dumbre
2021-11-16 15:08 ` [PATCH v9 1/5] device property: Add fwnode_iomap() Anand Ashok Dumbre
2021-11-16 17:07 ` Andy Shevchenko
2021-11-16 15:08 ` [PATCH v9 2/5] arm64: zynqmp: DT: Add Xilinx AMS node Anand Ashok Dumbre
2021-11-16 17:39 ` Andy Shevchenko
2021-11-16 18:55 ` Anand Ashok Dumbre
2021-11-16 15:08 ` [PATCH v9 3/5] iio: adc: Add Xilinx AMS driver Anand Ashok Dumbre
2021-11-16 17:38 ` Andy Shevchenko
2021-11-16 20:29 ` Anand Ashok Dumbre
2021-11-17 12:48 ` Andy Shevchenko
2021-11-16 15:08 ` [PATCH v9 4/5] dt-bindings: iio: adc: Add Xilinx AMS binding documentation Anand Ashok Dumbre
2021-11-16 15:08 ` [PATCH v9 5/5] MAINTAINERS: Add maintainer for xilinx-ams Anand Ashok Dumbre
2021-11-16 17:41 ` Andy Shevchenko
2021-11-17 14:34 ` Anand Ashok Dumbre
2021-11-17 15:17 ` Andy Shevchenko
2021-11-17 16:05 ` Joe Perches
2021-11-17 17:08 ` Andy Shevchenko
2021-11-17 18:46 ` Joe Perches
2021-11-17 19:28 ` Andy Shevchenko [this message]
2021-11-17 23:06 ` Joe Perches
2021-11-17 21:57 ` Anand Ashok Dumbre
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=YZVX9R/TMvkPwuuF@smile.fi.intel.com \
--to=andy.shevchenko@gmail.com \
--cc=ANANDASH@xilinx.com \
--cc=git@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jic23@kernel.org \
--cc=joe@perches.com \
--cc=lars@metafoo.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michals@xilinx.com \
--cc=rafael@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