From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Adrian Huang <adrianhuang0701@gmail.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Jan Dabros <jsd@semihalf.com>,
linux-i2c@vger.kernel.org, Adrian Huang <ahuang12@lenovo.com>,
Dong Wang <wangdong28@lenovo.com>
Subject: Re: [PATCH v2 1/1] i2c: designware: Fix wrong setting for {ss,fs,hs}_{h,l}cnt registers
Date: Mon, 12 Aug 2024 20:13:08 +0300 [thread overview]
Message-ID: <ZrpCpLYzCBTx0Mz6@smile.fi.intel.com> (raw)
In-Reply-To: <di6c5rvbjapddcndjs7jzqia3nki2qzmzrsmutldi4q55wile7@yyo6be3s57zj>
On Mon, Aug 05, 2024 at 07:26:55PM +0200, Andi Shyti wrote:
> Hi Adrian,
>
> > Link: https://lore.kernel.org/linux-i2c/8295cbe1-a7c5-4a35-a189-5d0bff51ede6@linux.intel.com/
> > Suggested-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
> > Signed-off-by: Adrian Huang <ahuang12@lenovo.com>
> > Reported-by: Dong Wang <wangdong28@lenovo.com>
> > Tested-by: Dong Wang <wangdong28@lenovo.com>
>
> At first I thought that we need a Fixes tag, but on a second
> thought I judged this more as a behavioural fix. Please, let me
> konw if you think we want to have the Fixes tag here.
>
> Meantime, I'm going to re-arrange the tag section. It's common to
> sort the tags in a chronological order:
>
> Reported-by: (it first gets reported)
> Suggested-by: (then someone suggested the fix)
> Signed-off-by: (then someone implemented the fix)
> Tested-by: (finally someone tested it)
> Link: (as reference)
If you use `b4`, you may configure it to do this automatically and keep nice
with contributors :-)
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-08-12 17:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 13:01 [PATCH v2 1/1] i2c: designware: Fix wrong setting for {ss,fs,hs}_{h,l}cnt registers Adrian Huang
2024-08-05 14:27 ` Jarkko Nikula
2024-08-05 17:26 ` Andi Shyti
2024-08-06 12:10 ` Huang Adrian
2024-08-12 17:13 ` Andy Shevchenko [this message]
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=ZrpCpLYzCBTx0Mz6@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=adrianhuang0701@gmail.com \
--cc=ahuang12@lenovo.com \
--cc=andi.shyti@kernel.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=jsd@semihalf.com \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=wangdong28@lenovo.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