linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Dąbroś" <jsd@semihalf.com>
To: Wolfram Sang <wsa@kernel.org>, Jan Dabros <jsd@semihalf.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-i2c <linux-i2c@vger.kernel.org>,
	Jarkko Nikula <jarkko.nikula@linux.intel.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Raul E Rangel <rrangel@chromium.org>,
	"Easow, Nimesh" <Nimesh.Easow@amd.com>,
	upstream@semihalf.com
Subject: Re: [PATCH] i2c: designware: Modify timing parameters for amdpsp mailbox
Date: Mon, 16 May 2022 15:34:13 +0200	[thread overview]
Message-ID: <CAOtMz3PWNOwTzmLB4d5tmRP5L6zg2ELcth8fd6_8vEEP7+=WoA@mail.gmail.com> (raw)
In-Reply-To: <YnLaOkzTA1dUrMkc@kunai>

śr., 4 maj 2022 o 21:55 Wolfram Sang <wsa@kernel.org> napisał(a):
>
> On Thu, Apr 28, 2022 at 02:26:51PM +0200, Jan Dabros wrote:
> > Adjust retry period and timeout values for x86-PSP mailbox based on the
> > typical I2C traffic generated by PSP. In order to limit the possibility
> > of timeouts, x86 should reduce the interval between retries as well as
> > increase overall time after which it gives up.
> >
> > Signed-off-by: Jan Dabros <jsd@semihalf.com>
>
> Applied to for-next, thanks! Let me know if you think this is a bugfix
> and should be in for-current.

Sorry for the late response! I believe this is not necessary to
include this patch in for-current. Thanks.

Best Regards,
Jan

      reply	other threads:[~2022-05-16 13:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28 12:26 [PATCH] i2c: designware: Modify timing parameters for amdpsp mailbox Jan Dabros
2022-04-28 13:07 ` Jarkko Nikula
2022-04-28 13:42   ` Jan Dąbroś
2022-05-04 19:55 ` Wolfram Sang
2022-05-16 13:34   ` Jan Dąbroś [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='CAOtMz3PWNOwTzmLB4d5tmRP5L6zg2ELcth8fd6_8vEEP7+=WoA@mail.gmail.com' \
    --to=jsd@semihalf.com \
    --cc=Nimesh.Easow@amd.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rrangel@chromium.org \
    --cc=upstream@semihalf.com \
    --cc=wsa@kernel.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;
as well as URLs for NNTP newsgroup(s).