From: Vinod Koul <vinod.koul@intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Sanyog Kale <sanyog.r.kale@intel.com>
Subject: Re: [GIT PULL]: soundwire updates
Date: Mon, 8 Jan 2018 22:23:32 +0530 [thread overview]
Message-ID: <20180108165332.GH18649@localhost> (raw)
In-Reply-To: <20180108132013.GA13067@kroah.com>
On Mon, Jan 08, 2018 at 02:20:13PM +0100, Greg KH wrote:
> On Fri, Jan 05, 2018 at 03:27:16PM +0530, Vinod Koul wrote:
> > Hey Greg,
> >
> > Please PULL to get three patches for static checks which people have
> > found. These have been tested by Fengguang's kbuildbot.
> >
> > The following changes since commit 1443f5b4fb451fdc894e4845ca67b370ed897a94:
> >
> > MAINTAINERS: Add SoundWire entry (2017-12-19 11:32:35 +0100)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/firmware.git soundwire-next
> >
> > for you to fetch changes up to c53a11d0ac0ed05f5569fa4396acb6b787ae8ac7:
> >
> > soundwire: Fix typo in return value check of sdw_read() (2018-01-03 08:53:46 +0530)
> >
> > ----------------------------------------------------------------
> > Colin Ian King (2):
> > soundwire: fix sign extension when shifting buf[2] 24 places
> > soundwire: intel: fix missing assignment to ret
> >
> > Wei Yongjun (1):
> > soundwire: Fix typo in return value check of sdw_read()
> >
> > drivers/soundwire/bus.c | 14 +++++++-------
> > drivers/soundwire/intel.c | 2 +-
> > 2 files changed, 8 insertions(+), 8 deletions(-)
>
> Please just send me patches for now until I trust you to send patches in
> that I don't have to review :)
Fair enough, I have sent these to you
--
~Vinod
prev parent reply other threads:[~2018-01-08 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 9:57 [GIT PULL]: soundwire updates Vinod Koul
2018-01-08 13:20 ` Greg KH
2018-01-08 16:53 ` Vinod Koul [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=20180108165332.GH18649@localhost \
--to=vinod.koul@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sanyog.r.kale@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