public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	linux-i2c <linux-i2c@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] i2c-host-fixes for v6.12-rc1
Date: Fri, 27 Sep 2024 18:45:06 +0300	[thread overview]
Message-ID: <ZvbTAl5uYbMcVI6m@black.fi.intel.com> (raw)
In-Reply-To: <auogjhzhbs2w45ptdkl5ceyxsm7apyfi5wmfv3iwuzfh47pl6f@4nnrnpqqlum2>

On Fri, Sep 27, 2024 at 12:09:36PM +0200, Andi Shyti wrote:

...

> ----------------------------------------------------------------
> The DesignWare driver now has the correct ENABLE-ABORT sequence,
> ensuring ABORT can always be sent when needed.
> 
> In the SynQuacer controller we now check for PCLK as an optional
> clock, allowing ACPI to directly provide the clock rate.
> 
> The recent KEBA driver required a dependency fix in Kconfig.
> 
> The XIIC driver now has a corrected power suspend sequence.

While tag message looks nice here, I think it still has to follow the
same (as in the commit message) pattern, i.e.

$SUMMARY
...blank line...
$DESCRIPTION

Why? Because the Web representation of the message looks weird on the
Web. Compare
https://git.kernel.org/pub/scm/linux/kernel/git/pinctrl/intel.git/tag/?h=intel-pinctrl-v6.12-1
and yours
https://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux.git/tag/?h=i2c-host-fixes-6.12-rc1

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2024-09-27 15:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27 10:09 [GIT PULL] i2c-host-fixes for v6.12-rc1 Andi Shyti
2024-09-27 15:45 ` Andy Shevchenko [this message]
2024-09-27 16:01   ` Andi Shyti

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=ZvbTAl5uYbMcVI6m@black.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=andi.shyti@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.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