All of lore.kernel.org
 help / color / mirror / Atom feed
From: kgene@kernel.org
To: 'Tomasz Figa' <t.figa@samsung.com>, 'Olof Johansson' <olof@lixom.net>
Cc: 'Mark Brown' <broonie@kernel.org>,
	'Tomasz Figa' <tomasz.figa@gmail.com>,
	arm@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org
Subject: RE: [GIT PULL] s3c64xx dmaengine conversion
Date: Thu, 05 Dec 2013 20:48:03 +0900	[thread overview]
Message-ID: <000401cef1af$dcdfd330$969f7990$@kernel.org> (raw)
In-Reply-To: <2721712.y1VtH8x62I@amdc1227>

Tomasz Figa wrote:
> 
> On Wednesday 04 of December 2013 13:38:39 Olof Johansson wrote:
> > On Sun, Nov 24, 2013 at 6:50 AM, Mark Brown <broonie@kernel.org> wrote:
> > > The following changes since commit
> 6ce4eac1f600b34f2f7f58f9cd8f0503d79e42ae:
> > >
> > >   Linux 3.13-rc1 (2013-11-22 11:30:55 -0800)
> > >
> > > are available in the git repository at:
> > >
> > >   git://git.kernel.org/pub/scm/linux/kernel/git/broonie/misc.git
> tags/s3c64xx-dmaengine
> > >
> > > for you to fetch changes up to
> 3faecea70b0d6d050e0ae911032ec340341dc389:
> > >
> > >   spi: s3c64xx: Always select S3C64XX_PL080 when ARCH_S3C64XX is
> enabled (2013-11-24 14:38:25 +0000)
> > >
> > > ----------------------------------------------------------------
> > > ARM: s3c64xx: Convert to dmaengine
> > >
> > > This series of commits from Tomasz converting s3c64xx to use dmaengine
> > > rather than the old s3c-dma API missed the v3.13 merge window - Kukjin
> > > said that he'd applied it (which should mean it's OK from a review
> point
> > > of view) but it didn't make it into -next or a pull request.
> > >
> > > Since a s3c64xx based system is one of my primary development
> platforms
> > > it'd be really helpful if I could merge this into both ASoC and SPI,
> > > I've got some patches for ASoC ready to go converting to use dmaengine
> > > directly which help with multiplatform and there's some other
> dmaengine
> > > work for SPI in progress too.  I've therefore made this signed tag,
> it'd
> > > be great if it could be merged into both arm-soc and those two trees.
> > >
> > > ----------------------------------------------------------------
> > >
> > > I'm open to other ideas for doing this, I'd just really like to see
> the
> > > code building on this go in this cycle so anything that accomplishes
> > > that is good for me.
> >
> > It's been 10 days and Kukjin hasn't moved on this, nor replied. I'm
> > going to merge it into arm-soc as samsung/s3c64xx-dmaengine ->
> > next/drivers so that you can use the branch as a base for your work.
> 
Oops, I have no idea why I missed that :-(
Sorry about that. Olof, thanks for your taking anyway.

- Kukjin

> OK, thanks.
> 
> Best regards,
> Tomasz

WARNING: multiple messages have this Message-ID (diff)
From: kgene@kernel.org (kgene at kernel.org)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] s3c64xx dmaengine conversion
Date: Thu, 05 Dec 2013 20:48:03 +0900	[thread overview]
Message-ID: <000401cef1af$dcdfd330$969f7990$@kernel.org> (raw)
In-Reply-To: <2721712.y1VtH8x62I@amdc1227>

Tomasz Figa wrote:
> 
> On Wednesday 04 of December 2013 13:38:39 Olof Johansson wrote:
> > On Sun, Nov 24, 2013 at 6:50 AM, Mark Brown <broonie@kernel.org> wrote:
> > > The following changes since commit
> 6ce4eac1f600b34f2f7f58f9cd8f0503d79e42ae:
> > >
> > >   Linux 3.13-rc1 (2013-11-22 11:30:55 -0800)
> > >
> > > are available in the git repository at:
> > >
> > >   git://git.kernel.org/pub/scm/linux/kernel/git/broonie/misc.git
> tags/s3c64xx-dmaengine
> > >
> > > for you to fetch changes up to
> 3faecea70b0d6d050e0ae911032ec340341dc389:
> > >
> > >   spi: s3c64xx: Always select S3C64XX_PL080 when ARCH_S3C64XX is
> enabled (2013-11-24 14:38:25 +0000)
> > >
> > > ----------------------------------------------------------------
> > > ARM: s3c64xx: Convert to dmaengine
> > >
> > > This series of commits from Tomasz converting s3c64xx to use dmaengine
> > > rather than the old s3c-dma API missed the v3.13 merge window - Kukjin
> > > said that he'd applied it (which should mean it's OK from a review
> point
> > > of view) but it didn't make it into -next or a pull request.
> > >
> > > Since a s3c64xx based system is one of my primary development
> platforms
> > > it'd be really helpful if I could merge this into both ASoC and SPI,
> > > I've got some patches for ASoC ready to go converting to use dmaengine
> > > directly which help with multiplatform and there's some other
> dmaengine
> > > work for SPI in progress too.  I've therefore made this signed tag,
> it'd
> > > be great if it could be merged into both arm-soc and those two trees.
> > >
> > > ----------------------------------------------------------------
> > >
> > > I'm open to other ideas for doing this, I'd just really like to see
> the
> > > code building on this go in this cycle so anything that accomplishes
> > > that is good for me.
> >
> > It's been 10 days and Kukjin hasn't moved on this, nor replied. I'm
> > going to merge it into arm-soc as samsung/s3c64xx-dmaengine ->
> > next/drivers so that you can use the branch as a base for your work.
> 
Oops, I have no idea why I missed that :-(
Sorry about that. Olof, thanks for your taking anyway.

- Kukjin

> OK, thanks.
> 
> Best regards,
> Tomasz

  reply	other threads:[~2013-12-05 11:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-24 14:50 [GIT PULL] s3c64xx dmaengine conversion Mark Brown
2013-11-24 14:50 ` Mark Brown
2013-12-04 21:38 ` Olof Johansson
2013-12-04 21:38   ` Olof Johansson
2013-12-05 11:34   ` Tomasz Figa
2013-12-05 11:34     ` Tomasz Figa
2013-12-05 11:48     ` kgene [this message]
2013-12-05 11:48       ` kgene at kernel.org

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='000401cef1af$dcdfd330$969f7990$@kernel.org' \
    --to=kgene@kernel.org \
    --cc=arm@kernel.org \
    --cc=broonie@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=t.figa@samsung.com \
    --cc=tomasz.figa@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.