From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/20 v2][RFC] arm64: Salvator-X sound support
Date: Fri, 18 Sep 2015 00:08:56 +0000 [thread overview]
Message-ID: <20150918000854.GA12858@verge.net.au> (raw)
In-Reply-To: <87vbb97kci.wl%kuninori.morimoto.gx@renesas.com>
On Thu, Sep 17, 2015 at 11:43:48PM +0000, Kuninori Morimoto wrote:
>
> Hi Simon
>
> > > > Do you have any thoughts the above patches going into topic branches?
> > > > It seems a bit messy but possible from my light analysis so far.
> > >
> > > what does it mean ?
> > > What/Which is messy ?
> >
> > Sorry for my poor choice of words. I was not referring to the code
> > itself, rather that the patchset doesn't appear to map well
> > to a single topic branch.
> >
> > What I see is something like this:
> >
> > 1) dmaengine core topic
> > 2,3) ak4613 driver topic
> > 5-18) i2c+sound integration topics
> > 19,20) i2c driver topic
> >
> > I think the above can be constructed if you think it is worthwhile.
> > There are of course other possibilities.
>
> Ahh, OK I see
> I need to send v3 patch-set. Then, I will separate these for each topics
> Does it clear for you ?
Thanks, I think that would help.
prev parent reply other threads:[~2015-09-18 0:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 4:19 [PATCH 0/20 v2][RFC] arm64: Salvator-X sound support Kuninori Morimoto
2015-09-17 4:47 ` Kuninori Morimoto
2015-09-17 7:37 ` Simon Horman
2015-09-17 9:47 ` Kuninori Morimoto
2015-09-17 23:25 ` Simon Horman
2015-09-17 23:43 ` Kuninori Morimoto
2015-09-18 0:08 ` Simon Horman [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=20150918000854.GA12858@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@vger.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