DMA Engine development
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: dmaengine@vger.kernel.org, Viresh Kumar <vireshk@kernel.org>,
	Vinod Koul <vkoul@kernel.org>
Subject: Re: [PATCH] dmaengine: dw: Update Intel Elkhart Lake Service Engine acronym
Date: Tue, 13 Aug 2019 17:45:00 +0300	[thread overview]
Message-ID: <20190813144500.GI30120@smile.fi.intel.com> (raw)
In-Reply-To: <82882d82-57e7-dabc-93af-6ec52c3fbc89@linux.intel.com>

On Tue, Aug 13, 2019 at 05:17:24PM +0300, Jarkko Nikula wrote:
> On 8/13/19 5:07 PM, Andy Shevchenko wrote:
> > On Tue, Aug 13, 2019 at 11:06:02AM +0300, Jarkko Nikula wrote:
> > > Intel Elkhart Lake Offload Service Engine (OSE) will be called as
> > > Intel(R) Programmable Services Engine (Intel(R) PSE) in documentation.
> > > 
> > > Update the comment here accordingly.
> > 
> > Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > 
> > Seems similar we need for UART.
> > 
> You mean a0d993e8c143 ("serial: 8250_lpss: Enable HS UART on Elkhart Lake")?
> No Code or comment on that commit mention OSE, only commit log.

Ah, we can't fix commit messages.
Thanks for checking!

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2019-08-13 14:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-13  8:06 [PATCH] dmaengine: dw: Update Intel Elkhart Lake Service Engine acronym Jarkko Nikula
2019-08-13 14:07 ` Andy Shevchenko
2019-08-13 14:17   ` Jarkko Nikula
2019-08-13 14:45     ` Andy Shevchenko [this message]
2019-08-19  8:32 ` Viresh Kumar
2019-08-20 11:09 ` Vinod Koul

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=20190813144500.GI30120@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=vireshk@kernel.org \
    --cc=vkoul@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