From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Amit Tomer <amittomer25@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
u-boot@linux.nxdi.nxp.com, Hui Song <hui.song_1@nxp.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org, jiafei.pan@nxp.com,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v1 2/3] armv8: gpio: add gpio feature
Date: Sat, 9 May 2020 19:18:45 +0100 [thread overview]
Message-ID: <20200509181845.GH1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <CABHD4K_tPkCherpY5zUtxV1wcKc=7aj3ayr9yxG-sLFZeMf3Dw@mail.gmail.com>
On Sat, May 09, 2020 at 11:34:59PM +0530, Amit Tomer wrote:
> > From what I can tell, these patches are not for the kernel. The
> > filenames don't match th kernel layout.
>
> These files looks to be from U-boot, and must be intended for U-boot
> as I see U-boot mailing address in recipient's address?
So why is it copied to:
devicetree@vger.kernel.org - a kernel mailing list
linux-kernel@vger.kernel.org - the main kernel mailing list
linux-gpio@vger.kernel.org - the gpio driver kernel mailing list
linux-arm-kernel@lists.infradead.org - the ARM kernel mailing list
Given that it includes four kernel mailing lists (ok, devicetree
may be argued to have a wider application), then I don't think the
conclusion that "it's for u-boot, because there's _one_ u-boot
mailing list in the recipients" is particularly obvious.
The author really needs to state that up front if they're sending
it to a wide audeience, rather than leaving people to guess, thereby
potentially wasting their time.
Not only did Andrew review the patch as if it were for the kernel,
but I also wasted time on this as well when I double-took the
ifdefs, and wanted to check the current driver in the kernel.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 10.2Mbps down 587kbps up
WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Amit Tomer <amittomer25@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
u-boot@linux.nxdi.nxp.com, Hui Song <hui.song_1@nxp.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org, jiafei.pan@nxp.com,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v1 2/3] armv8: gpio: add gpio feature
Date: Sat, 9 May 2020 19:18:45 +0100 [thread overview]
Message-ID: <20200509181845.GH1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <CABHD4K_tPkCherpY5zUtxV1wcKc=7aj3ayr9yxG-sLFZeMf3Dw@mail.gmail.com>
On Sat, May 09, 2020 at 11:34:59PM +0530, Amit Tomer wrote:
> > From what I can tell, these patches are not for the kernel. The
> > filenames don't match th kernel layout.
>
> These files looks to be from U-boot, and must be intended for U-boot
> as I see U-boot mailing address in recipient's address?
So why is it copied to:
devicetree@vger.kernel.org - a kernel mailing list
linux-kernel@vger.kernel.org - the main kernel mailing list
linux-gpio@vger.kernel.org - the gpio driver kernel mailing list
linux-arm-kernel@lists.infradead.org - the ARM kernel mailing list
Given that it includes four kernel mailing lists (ok, devicetree
may be argued to have a wider application), then I don't think the
conclusion that "it's for u-boot, because there's _one_ u-boot
mailing list in the recipients" is particularly obvious.
The author really needs to state that up front if they're sending
it to a wide audeience, rather than leaving people to guess, thereby
potentially wasting their time.
Not only did Andrew review the patch as if it were for the kernel,
but I also wasted time on this as well when I double-took the
ifdefs, and wanted to check the current driver in the kernel.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 10.2Mbps down 587kbps up
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-05-09 18:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 10:39 [PATCH v1 1/3] gpio: mpc8xxx: support fsl-layerscape platform Hui Song
2020-05-09 10:39 ` Hui Song
2020-05-09 10:39 ` [PATCH v1 2/3] armv8: gpio: add gpio feature Hui Song
2020-05-09 10:39 ` Hui Song
2020-05-09 15:33 ` Andrew Lunn
2020-05-09 15:33 ` Andrew Lunn
2020-05-09 17:27 ` Russell King - ARM Linux admin
2020-05-09 17:27 ` Russell King - ARM Linux admin
2020-05-09 18:04 ` Amit Tomer
2020-05-09 18:04 ` Amit Tomer
2020-05-09 18:18 ` Russell King - ARM Linux admin [this message]
2020-05-09 18:18 ` Russell King - ARM Linux admin
2020-05-09 18:26 ` Russell King - ARM Linux admin
2020-05-09 18:26 ` Russell King - ARM Linux admin
2020-05-09 18:34 ` Amit Tomer
2020-05-09 18:34 ` Amit Tomer
2020-05-09 10:39 ` [PATCH v1 3/3] dm: armv8: gpio: include <asm/arch/gpio.h> for fsl-layerscape Hui Song
2020-05-09 10:39 ` Hui Song
2020-05-09 15:24 ` [PATCH v1 1/3] gpio: mpc8xxx: support fsl-layerscape platform Andrew Lunn
2020-05-09 15:24 ` Andrew Lunn
-- strict thread matches above, loose matches on Subject: below --
2020-05-09 10:35 Hui Song
2020-05-09 10:35 ` [PATCH v1 2/3] armv8: gpio: add gpio feature Hui Song
2020-05-09 10:35 ` Hui Song
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=20200509181845.GH1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=amittomer25@gmail.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=hui.song_1@nxp.com \
--cc=jiafei.pan@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=u-boot@linux.nxdi.nxp.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.