From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Andrew Lunn <andrew@lunn.ch>, Haibo Chen <haibo.chen@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Jim Reinhart <jimr@tekvox.com>,
James Autry <jautry@tekvox.com>,
Matthew Maron <matthewm@tekvox.com>
Subject: Re: [PATCH] mmc: sdhci-esdhc-imx: improve ESDHC_FLAG_ERR010450
Date: Thu, 17 Aug 2023 18:44:04 +0200 [thread overview]
Message-ID: <116308f2-2133-5953-802d-6da562c81af1@benettiengineering.com> (raw)
In-Reply-To: <CAPDyKFq9VpSDuD1itDPZ0cYdRJuHvYcK=+Si-u1YkDqQhBAcQQ@mail.gmail.com>
Hello Ulf,
On 16/08/23 23:36, Ulf Hansson wrote:
> On Wed, 16 Aug 2023 at 19:14, Giulio Benetti
> <giulio.benetti@benettiengineering.com> wrote:
>>
>> Hello Ulf, and All,
>>
>> +Cc Andrew Lunn,
>>
>> On 16/08/23 11:52, Ulf Hansson wrote:
>>> On Fri, 11 Aug 2023 at 23:49, Giulio Benetti
>>> <giulio.benetti@benettiengineering.com> wrote:
>>>>
>>>> Errata ERR010450 only shows up if voltage is 1.8V, but if the device is
>>>> supplied by 3v3 the errata can be ignored. So let's check for if quirk
>>>> SDHCI_QUIRK2_NO_1_8_V is defined or not before limiting the frequency.
>>>>
>>>> Sponsored by: Tekvox Inc.
>>>
>>> Didn't know we have this kind of tag. Can you point me to the
>>> documentation of it?
>>
>> I've been pointed by Andew Lunn almost the same question here:
>> https://lore.kernel.org/lkml/859ff6a9-3ba9-ea2e-7b85-01813c5df0dd@broadcom.com/t/
>>
>> and also asked to update:
>> Documentation/process/submitting-patches.rst
>>
>> I've taken inspiration by this commit:
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=73c289bac05919286f8c7e1660fcaf6ec0468363
>>
>> where there is "Sponsored by:" and not "Sponsored-by:" otherwise
>> checkpatch.pl script complains about it.
>>
>> Other commits already have that sort of tag.
>
> Yes, but that seems silly to me.
>
> We should not be using tags in this way. First there needs to be an
> agreement of what kind of tags we should allow in the commit messages,
> before we start using them.
>
>>
>> I could add Sponsored-by tag documentation and in checkpatch.pl script
>> as well as other possible scripts where required as pointed by Andrew.
>>
>> I think this is a good way to give credits to companies that sponsor
>> patches and it could be more interesting for companies in general to
>> pay someone to upstream patches because they have their name on it.
>> Otherwise it's not an everyday task to add a driver from scratch
>> and write in the top comment that is sponsored by some company.
>> Also now there is SPDX so that part would be dropped too.
>>
>> What do you All think about this? Do I go for a RFC patchset to add
>> the Sponsored-by: tag?
>
> My opinion is just one voice here, so at this point it doesn't really
> matter what I think.
>
> If *you* think this is a good idea, I encourage you to submit an RFC
> to the kernel docs for this. In this way we can collect the comments
> and see if people think this is a good idea.
Ok, I will go with a RFC soon,
> That said, do you want me to apply $subject patch without the tag or
> would you rather proceed with submitting an RFC first?
It would be great if you can apply the patch without the tag please.
Thank you
Best regards
--
Giulio Benetti
CEO&CTO@Benetti Engineering sas
next prev parent reply other threads:[~2023-08-17 16:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 21:48 [PATCH] mmc: sdhci-esdhc-imx: improve ESDHC_FLAG_ERR010450 Giulio Benetti
2023-08-15 12:07 ` Adrian Hunter
2023-08-16 1:21 ` Bough Chen
2023-08-16 5:44 ` Adrian Hunter
2023-08-16 9:52 ` Ulf Hansson
2023-08-16 17:14 ` Giulio Benetti
2023-08-16 21:36 ` Ulf Hansson
2023-08-17 16:44 ` Giulio Benetti [this message]
2023-08-18 9:30 ` Ulf Hansson
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=116308f2-2133-5953-802d-6da562c81af1@benettiengineering.com \
--to=giulio.benetti@benettiengineering.com \
--cc=adrian.hunter@intel.com \
--cc=andrew@lunn.ch \
--cc=festevam@gmail.com \
--cc=haibo.chen@nxp.com \
--cc=jautry@tekvox.com \
--cc=jimr@tekvox.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=matthewm@tekvox.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=ulf.hansson@linaro.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