mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Lee Jones <lee.jones@linaro.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Jarkko Nikula <jarkko.nikula@linux.intel.com>,
	Len Brown <lenb@kernel.org>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] mfd: intel_soc_pmic: Differentiate between Bay and Cherry Trail CRC variants
Date: Fri, 21 Jul 2017 20:41:05 +0200	[thread overview]
Message-ID: <536760e3-c25d-740c-4705-758131d66581@redhat.com> (raw)
In-Reply-To: <20170718071725.irultqetstthnozh@dell>

Hi,

On 18-07-17 09:17, Lee Jones wrote:
> On Mon, 17 Jul 2017, Andy Shevchenko wrote:
> 
>> On Mon, 2017-07-17 at 11:59 +0100, Lee Jones wrote:
>>> On Sat, 01 Jul 2017, Hans de Goede wrote:
>>>
>>>> Both Bay and Cherry Trail devices may be used together with a
>>>> Crystal Cove
>>>> PMIC. Each platform has its own variant of the PMIC, which both use
>>>> the
>>>> same ACPI HID, but they are not 100% compatible.
>>>>
>>>> This commits makes the intel_soc_pmic_core code check the _HRV of
>>>> the
>>>> ACPI-firmware-node and selects intel_soc_pmic_config_byt_crc resp.
>>>> intel_soc_pmic_config_cht_crc based on this.
>>>>
>>>> This fixes the Bay Trail specific ACPI OpRegion code causing
>>>> problems
>>>> on Cherry Trail devices. Specifically this was causing the external
>>>> microsd slot on a Dell Venue 8 5855 (Cherry Trail version) to not
>>>> work
>>>> and the eMMC to become unreliable and throw lots of errors.
>>>>
>>>> Reported-and-tested-by: russianneuromancer <russianneuromancer@ya.ru
>>>>>
>>>
>>> Real names only please.
>>>
>>> What is the name of this reporter/tester?
>>
>> No one knows, I think.
> 
> Then I don't think we can credit him/her for their efforts.
> SubmittingPatches clearly states "no pseudonyms or anonymous
> contributions".  Either write to them and ask for their real name so
> that they can be credited, or remove the line.

russianneuromancer has been a great help with reporting and testing
many Bay Trail / Cherry Trail issues. He does not want to use his
real name.

AFAIK the Real Name rule only applies tot he Signed-off-by tag, no
other subsys-maintainers have had problems with listing him as
reporter / tester using his alias.

The Real Name only rule is part of "11) Sign your work — the
Developer’s Certificate of Origin" of :

https://www.kernel.org/doc/html/latest/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin

Which is all about the S-o-b tag. If you despite this still want
a new version with russianneuromancer's Reported-and-tested-by
dropped let me know and I will send a new version.

Regards,

Hans

  reply	other threads:[~2017-07-21 18:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-01 10:13 [PATCH 1/2] mfd: intel_soc_pmic: Export separate mfd-cell configs for BYT and CHT Hans de Goede
2017-07-01 10:13 ` [PATCH 2/2] mfd: intel_soc_pmic: Differentiate between Bay and Cherry Trail CRC variants Hans de Goede
2017-07-02 12:34   ` Andy Shevchenko
2017-07-17 10:59   ` Lee Jones
2017-07-17 13:23     ` Andy Shevchenko
2017-07-18  7:17       ` Lee Jones
2017-07-21 18:41         ` Hans de Goede [this message]
2017-07-21 19:23           ` Andy Shevchenko
2017-07-02 12:34 ` [PATCH 1/2] mfd: intel_soc_pmic: Export separate mfd-cell configs for BYT and CHT Andy Shevchenko
2017-07-17 10:59 ` Lee Jones

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=536760e3-c25d-740c-4705-758131d66581@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=lee.jones@linaro.org \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®