linux-samsung-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sylwester Nawrocki <s.nawrocki@samsung.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
	Kevin Hilman <khilman@kernel.org>,
	arm@kernel.org, Kukjin Kim <kgene@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Javier Martinez Canillas <javier@osg.samsung.com>
Subject: Re: [GIT PULL] ARM: exynos: Late mach/soc for v4.10
Date: Mon, 2 Jan 2017 17:56:54 +0200	[thread overview]
Message-ID: <20170102155654.oey6c542vjcqyit2@kozik-lap> (raw)
In-Reply-To: <5b0e55c8-01db-3f02-3526-2f71f4a73d88@samsung.com>

On Mon, Jan 02, 2017 at 10:20:21AM +0100, Sylwester Nawrocki wrote:
> On 12/30/2016 04:53 PM, Krzysztof Kozlowski wrote:
> > 
> > Any comments on this? I guess it won't come as late-late-4.10, so can
> > you pull it for v4.11?
>  
> >> Sylwester Nawrocki (1):
> >>       ARM: S3C24XX: Add DMA slave maps for remaining s3c24xx SoCs
> 
> We need this patch in v4.10 to avoid possible I2S and MMC regressions
> on selected s3c24xx SoC, since the DMA clients are already modified.
> If the patch goes in only for v4.11 it would be good to mark it for 
> inclusion in v4.10 stable kernels.  

You didn't mention any strict dependencies when sending this patch...
What do you mean by "needing patch in v4.10"? Is the code already
not bisectable? Already broken?

Best regards,
Krzysztof

  reply	other threads:[~2017-01-02 15:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-17 19:32 [GIT PULL] ARM: exynos: Late mach/soc for v4.10 Krzysztof Kozlowski
2016-12-30 15:53 ` Krzysztof Kozlowski
     [not found]   ` <CGME20170102092044epcas1p3cbe831b7b6528f818b034d73c85dbe7d@epcas1p3.samsung.com>
2017-01-02  9:20     ` Sylwester Nawrocki
2017-01-02 15:56       ` Krzysztof Kozlowski [this message]
2017-01-02 17:25         ` Sylwester Nawrocki
2017-01-02 17:35           ` Krzysztof Kozlowski
2017-01-04 15:14 ` Arnd Bergmann

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=20170102155654.oey6c542vjcqyit2@kozik-lap \
    --to=krzk@kernel.org \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=javier@osg.samsung.com \
    --cc=kgene@kernel.org \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=s.nawrocki@samsung.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;
as well as URLs for NNTP newsgroup(s).