From: viresh.kumar@st.com (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] SPEAr: Use CLKDEV_INIT for defining clk_lookups
Date: Fri, 23 Mar 2012 15:26:42 +0530 [thread overview]
Message-ID: <4F6C48DA.9080005@st.com> (raw)
In-Reply-To: <201203230848.52010.arnd@arndb.de>
On 3/23/2012 2:18 PM, Arnd Bergmann wrote:
> Since we're in the middle of the merge window now, I would
> prefer not to pull any cosmetic changes or new features but
> instead just take the bug fix. Once -rc1 is done, we will
> start taking patches for v3.5.
>
Ok.
> If the second patch is actually required and nit just cosmetic,
> please provide a description why that is so.
It is just an cosmetic one. I posted it, so stefan can work over
it and i don't have to rework on it again. What's the preferred
way of handling such stuff during merge window?
> Finally, the branch you mentioned does not seem to be there
> on the server.
I am so sorry. Actually we have two interfaces to stlinux, one
is ST internal and other is external. I have pushed the branch
at the time i posted it, but stlinux site takes a bit to get
everything synched (i came to know this today only :( ).
> I recommend using 'git request-pull', which will actually check
> that the branch you refer to can be pulled and holds the right
> contents.
Sure.
--
Viresh
next prev parent reply other threads:[~2012-03-23 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 8:16 [PATCH] SPEAr: Use CLKDEV_INIT for defining clk_lookups Viresh Kumar
2012-03-23 8:48 ` Arnd Bergmann
2012-03-23 9:56 ` Viresh Kumar [this message]
2012-03-23 11:39 ` 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=4F6C48DA.9080005@st.com \
--to=viresh.kumar@st.com \
--cc=linux-arm-kernel@lists.infradead.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.