From: Vinod Koul <vinod.koul@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Takashi <tiwai@suse.de>, LKML <linux-kernel@vger.kernel.org>,
ALSA <alsa-devel@alsa-project.org>, Mark <broonie@kernel.org>,
Pierre <pierre-louis.bossart@linux.intel.com>,
patches.audio@intel.com, alan@linux.intel.com,
Charles Keepax <ckeepax@opensource.cirrus.com>,
Sagar Dharia <sdharia@codeaurora.org>,
srinivas.kandagatla@linaro.org, plai@codeaurora.org,
Sudheer Papothi <spapothi@codeaurora.org>
Subject: Re: [PATCH v6 00/14] soundwire: Add a new SoundWire subsystem
Date: Thu, 14 Dec 2017 16:23:20 +0530 [thread overview]
Message-ID: <20171214105320.GX18649@localhost> (raw)
In-Reply-To: <20171214073508.GA29585@kroah.com>
On Thu, Dec 14, 2017 at 08:35:08AM +0100, Greg Kroah-Hartman wrote:
> On Thu, Dec 14, 2017 at 11:19:31AM +0530, Vinod Koul wrote:
> > Changes in v6:
> > - Add reviewed/acked tags from Philippe, Pierre, Takashi and Greg
> > - Fix nitpicks from Takashi
> > - Drop the sysfs patch for now
>
> Wait, why drop the sysfs patch entirely? You need those attributes,
> right? You also need to document the existing sysfs files in
> Documentation/ABI/ for the class/device files you create in this patch
> series, so that needs to be done before this patch series can be
> accepted.
Well the sysfs patch is a standalone patch which contains the attributes. So
I dropped that "for this series" and plan to submit after reworking.
The rest of the code doesn't depend on it, so is fine.
I thought it is an okay kernel practice to drop patches with issues, merge the
rest and come back after fixing the issue. This is my plan for this as well.
Thanks
--
~Vinod
next prev parent reply other threads:[~2017-12-14 10:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 5:49 [PATCH v6 00/14] soundwire: Add a new SoundWire subsystem Vinod Koul
2017-12-14 5:49 ` [PATCH v6 01/14] Documentation: Add SoundWire summary Vinod Koul
2017-12-14 5:49 ` [PATCH v6 02/14] soundwire: Add SoundWire bus type Vinod Koul
2017-12-14 5:49 ` [PATCH v6 03/14] soundwire: Add Master registration Vinod Koul
2017-12-14 5:49 ` [PATCH v6 04/14] soundwire: Add MIPI DisCo property helpers Vinod Koul
2017-12-14 5:49 ` [PATCH v6 05/14] soundwire: Add SoundWire MIPI defined registers Vinod Koul
2017-12-14 5:49 ` [PATCH v6 06/14] soundwire: Add IO transfer Vinod Koul
2017-12-14 5:49 ` [PATCH v6 07/14] regmap: Add SoundWire bus support Vinod Koul
2018-01-05 17:04 ` Mark Brown
2018-01-05 17:22 ` [alsa-devel] " Pierre-Louis Bossart
2018-01-06 6:12 ` Vinod Koul
2018-01-06 6:11 ` Vinod Koul
2018-01-05 17:05 ` Mark Brown
2018-01-06 6:13 ` [alsa-devel] " Vinod Koul
2017-12-14 5:49 ` [PATCH v6 08/14] soundwire: Add Slave status handling helpers Vinod Koul
2017-12-14 5:49 ` [PATCH v6 09/14] soundwire: Add slave status handling Vinod Koul
2017-12-14 5:49 ` [PATCH v6 10/14] soundwire: cdns: Add cadence library Vinod Koul
2017-12-14 5:49 ` [PATCH v6 11/14] soundwire: cdns: Add sdw_master_ops and IO transfer support Vinod Koul
2017-12-14 5:49 ` [PATCH v6 12/14] soundwire: intel: Add Intel Master driver Vinod Koul
2017-12-14 5:49 ` [PATCH v6 13/14] soundwire: intel: Add Intel init module Vinod Koul
2017-12-14 5:49 ` [PATCH v6 14/14] MAINTAINERS: Add SoundWire entry Vinod Koul
2017-12-14 7:35 ` [PATCH v6 00/14] soundwire: Add a new SoundWire subsystem Greg Kroah-Hartman
2017-12-14 10:53 ` Vinod Koul [this message]
2017-12-14 12:49 ` Greg Kroah-Hartman
2017-12-14 13:18 ` Vinod Koul
2017-12-14 15:09 ` Mark Brown
2017-12-19 10:33 ` Greg Kroah-Hartman
2017-12-14 9:02 ` Philippe Ombredanne
2017-12-14 10:54 ` 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=20171214105320.GX18649@localhost \
--to=vinod.koul@intel.com \
--cc=alan@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches.audio@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=plai@codeaurora.org \
--cc=sdharia@codeaurora.org \
--cc=spapothi@codeaurora.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.de \
/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).