All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Naveen Krishna Ch
	<naveenkrishna.ch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Naveen Krishna Chatradhi
	<ch.naveen-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	"linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
	grundler-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	cpgs-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org
Subject: Re: [PATCH] i2c: exynos5: Initialise Samsung High Speed I2C controller early
Date: Wed, 21 May 2014 15:00:43 +0200	[thread overview]
Message-ID: <20140521130043.GA2628@katana> (raw)
In-Reply-To: <CAHfPSqCOnW4YGPfMfpBMbLSaiSxRN=CHJK6kYdkXMujKvNwAPA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 333 bytes --]


> Kindly, suggest a workable approach for all the subsystems.

Keep this patch out-of-tree? I know that probe ordering causes problems,
and that it needs major efforts. Yet, I understood that adding more and
more subsys_initcall to mainline is not going to help the process unless
essential. Using subsys_initcall has issues, too.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i2c: exynos5: Initialise Samsung High Speed I2C controller early
Date: Wed, 21 May 2014 15:00:43 +0200	[thread overview]
Message-ID: <20140521130043.GA2628@katana> (raw)
In-Reply-To: <CAHfPSqCOnW4YGPfMfpBMbLSaiSxRN=CHJK6kYdkXMujKvNwAPA@mail.gmail.com>


> Kindly, suggest a workable approach for all the subsystems.

Keep this patch out-of-tree? I know that probe ordering causes problems,
and that it needs major efforts. Yet, I understood that adding more and
more subsys_initcall to mainline is not going to help the process unless
essential. Using subsys_initcall has issues, too.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140521/59d62bb1/attachment.sig>

WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: Naveen Krishna Ch <naveenkrishna.ch@gmail.com>
Cc: Mark Brown <broonie@kernel.org>,
	Naveen Krishna Chatradhi <ch.naveen@samsung.com>,
	linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	"linux-samsung-soc@vger.kernel.org" 
	<linux-samsung-soc@vger.kernel.org>,
	sjg@chromium.org, grundler@chromium.org,
	linux-kernel@vger.kernel.org, cpgs@samsung.com
Subject: Re: [PATCH] i2c: exynos5: Initialise Samsung High Speed I2C controller early
Date: Wed, 21 May 2014 15:00:43 +0200	[thread overview]
Message-ID: <20140521130043.GA2628@katana> (raw)
In-Reply-To: <CAHfPSqCOnW4YGPfMfpBMbLSaiSxRN=CHJK6kYdkXMujKvNwAPA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 333 bytes --]


> Kindly, suggest a workable approach for all the subsystems.

Keep this patch out-of-tree? I know that probe ordering causes problems,
and that it needs major efforts. Yet, I understood that adding more and
more subsys_initcall to mainline is not going to help the process unless
essential. Using subsys_initcall has issues, too.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2014-05-21 13:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24 14:48 [PATCH] i2c: exynos5: Initialise Samsung High Speed I2C controller early Naveen Krishna Chatradhi
2014-04-24 14:48 ` Naveen Krishna Chatradhi
2014-04-24 14:48 ` Naveen Krishna Chatradhi
2014-04-24 16:25 ` Mark Brown
2014-04-24 16:25   ` Mark Brown
2014-04-25  4:58   ` Tushar Behera
2014-04-25  4:58     ` Tushar Behera
     [not found]   ` <20140424162558.GB12304-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-05-09 12:20     ` Naveen Krishna Ch
2014-05-09 12:20       ` Naveen Krishna Ch
2014-05-09 12:20       ` Naveen Krishna Ch
2014-05-09 13:51       ` Mark Brown
2014-05-09 13:51         ` Mark Brown
     [not found]         ` <20140509135153.GM12304-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-05-09 14:42           ` Naveen Krishna Ch
2014-05-09 14:42             ` Naveen Krishna Ch
2014-05-09 14:42             ` Naveen Krishna Ch
     [not found]             ` <CAHfPSqDSTyQXPT-NCZ2hE01qpdmaR54tbWCUYC_zSDGFp58+7g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-09 14:54               ` Mark Brown
2014-05-09 14:54                 ` Mark Brown
2014-05-09 14:54                 ` Mark Brown
2014-05-21 10:25                 ` Wolfram Sang
2014-05-21 10:25                   ` Wolfram Sang
2014-05-21 12:04                   ` Naveen Krishna Ch
2014-05-21 12:04                     ` Naveen Krishna Ch
     [not found]                     ` <CAHfPSqCOnW4YGPfMfpBMbLSaiSxRN=CHJK6kYdkXMujKvNwAPA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-21 13:00                       ` Wolfram Sang [this message]
2014-05-21 13:00                         ` Wolfram Sang
2014-05-21 13:00                         ` Wolfram Sang

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=20140521130043.GA2628@katana \
    --to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
    --cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=ch.naveen-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
    --cc=cpgs-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
    --cc=grundler-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=naveenkrishna.ch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.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 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.