From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/5] DTS: imx28: Copy imx28 device tree related files from Linux kernel (v5.1.2)
Date: Fri, 14 Jun 2019 14:09:53 +0200 [thread overview]
Message-ID: <20190614140953.587e6ffb@jawa> (raw)
In-Reply-To: <4408101a-90d3-0a8e-4d74-7d66e8de3275@denx.de>
On Fri, 14 Jun 2019 12:49:10 +0200
Marek Vasut <marex@denx.de> wrote:
> On 6/14/19 12:41 PM, Lukasz Majewski wrote:
> > Hi Marek,
> >
> >> On 6/14/19 8:49 AM, Lukasz Majewski wrote:
> >>> This commit copies from the Linux kernel (tag v5.1.2) i.MX28
> >>> related device tree files.
> >>>
> >>
> >> Linux 5.1.9 is already out,
> >
> > I will check if there are any differences and update.
> >
> >> commit hash is missing.
> >> Shouldn't the tags be something like "ARM: dts: imx" ? Fix the tags
> >> globally.
> >
> > With those tags it is indeed interesting.
> >
> > As fair as I know those are used by patman to indicate automatically
> > the receiver(s).
> >
> > One can see them defined in ./doc/git-mailrc
> >
> > And we now have "dts" - which is not defined there, but shows the
> > "purpose/target" subsystem.
> >
> > The "arm" causes sending mail to u-boot, Tom and Albert.
> > The "imx" to uboot and Stefano.
> >
> > This might be important if I did not used Series-cc: and Series-to:
> > from patman (which I did).
> >
> >
> > I would appreciate if there were any guidelines to use those tags
> > (there aren't any for Linux though, just there is an Maintainer's
> > "convention").
> >
> > By "convention" I mean a sorting rule in Maintainer's mail program
> > set arbitrarily to filter out not eligible patches :-)
>
> The general agreement was to stick with the linux tags, and that's
> what git log --oneline arch/arm/dts would indicate as well. Maybe
> patman needs to be fixed to stop inventing weird tags.
>
Simon, do you have any thoughts regarding patman's tag policy (after
the time that we do use patman) ?
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/20190614/c0e3a478/attachment.sig>
next prev parent reply other threads:[~2019-06-14 12:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 6:49 [U-Boot] [PATCH v2 0/5] DM: Convert i.MX28 gpio, pinmux, spi and eth drivers to DM/DTS Lukasz Majewski
2019-06-14 6:49 ` [U-Boot] [PATCH v2 1/5] DTS: imx28: Copy imx28 device tree related files from Linux kernel (v5.1.2) Lukasz Majewski
2019-06-14 10:25 ` Marek Vasut
2019-06-14 10:41 ` Lukasz Majewski
2019-06-14 10:49 ` Marek Vasut
2019-06-14 12:09 ` Lukasz Majewski [this message]
2019-06-14 6:49 ` [U-Boot] [PATCH v2 2/5] imx: net: Enable support for i.MX28 DM_ETH in the fec_mxc.c driver Lukasz Majewski
2019-06-14 6:49 ` [U-Boot] [PATCH v2 3/5] DM: mxs: gpio: Add support for DM/DTS in the mxs_gpio.c driver (DM_GPIO) Lukasz Majewski
2019-06-14 6:49 ` [U-Boot] [PATCH v2 4/5] imx: pinctrl: Add support for i.MX28 mxs pinctrl driver Lukasz Majewski
2019-06-14 6:49 ` [U-Boot] [PATCH v2 5/5] DM: spi: Add support DM/DTS for i.MX28 mxs SPI driver (DM_SPI conversion) Lukasz Majewski
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=20190614140953.587e6ffb@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