From: Greg KH <greg@kroah.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Par-Gunnar Hjalmdahl <par-gunnar.p.hjalmdahl@stericsson.com>,
devel@driverdev.osuosl.org,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Par-Gunnar Hjalmdahl <pghatwork@gmail.com>,
Arnd Bergmann <arnd@arndb.de>, Vitaly Wool <vitalywool@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-kernel@vger.kernel.org,
Lukasz Rymanowski <Lukasz.Rymanowski@tieto.com>,
linux-bluetooth@vger.kernel.org,
Pavan Savoy <pavan_savoy@sify.com>,
Lee Jones <lee.jones@linaro.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH v6] Add ST-Ericsson CG2900 driver
Date: Sun, 15 May 2011 09:32:57 -0700 [thread overview]
Message-ID: <20110515163257.GE1315@kroah.com> (raw)
In-Reply-To: <BANLkTinAtUQ8H1DQpqXxX_U4mLO617L3Eg@mail.gmail.com>
On Sun, May 15, 2011 at 12:20:51PM +0200, Linus Walleij wrote:
> 2011/5/10 Par-Gunnar Hjalmdahl <par-gunnar.p.hjalmdahl@stericsson.com>:
>
> > Patch created on next-20110510.
> > Compared to v5 this patch has the following update:
> > - Updated driver after changes to MFD interfaces in linux-next (from mfd_data
> > to platform_data).
> > - Changed platform specific file dependencies (included correct nomadik file).
>
> Sorry I don't know if all this will work, it's due to all the churn created by
> the current push to get stuff out of the ARM tree so not much to do.
>
> The Nomadik GPIO file was moved in next but I will take that code move
> out today, because the GPIO maintainer has told me he couldn't
> provide feedback on these patches in time for me to finalize the change
> for kernel 2.6.40. Thus it won't go into 2.6.40 and I must remove it
> from next.
>
> The MFD changes will *probably* happen, if you're thinking about the
> PRCMU movement etc.
>
> To merge into the staging tree right now, you need to base it off
> Gregs staging tree, which is where it'll be merged:
> http://git.kernel.org/?p=linux/kernel/git/gregkh/staging-2.6.git;a=summary
>
> Sorry about all the confusion, I think it's actually nobodys fault,
> it's just reflecting the fact that embedded drivers with deep
> platform dependencies are *really* *hard* to manage in staging.
That's why you should only use staging as a last resort, not as your
primary way of getting code into the kernel, especially for stuff with
a constantly changing in-kernel interface like you have pointed out
here.
Just do the "real work" first and get it merged the real way if at all
possible.
best of luck,
greg k-h
next prev parent reply other threads:[~2011-05-15 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 15:10 [PATCH v6] Add ST-Ericsson CG2900 driver Par-Gunnar Hjalmdahl
2011-05-15 10:20 ` Linus Walleij
2011-05-15 16:32 ` Greg KH [this message]
2011-05-15 17:29 ` Linus Walleij
2011-05-15 17:36 ` Greg KH
2011-05-15 17:59 ` Linus Walleij
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=20110515163257.GE1315@kroah.com \
--to=greg@kroah.com \
--cc=Lukasz.Rymanowski@tieto.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mathieu.poirier@linaro.org \
--cc=par-gunnar.p.hjalmdahl@stericsson.com \
--cc=pavan_savoy@sify.com \
--cc=pghatwork@gmail.com \
--cc=vitalywool@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox