From: Greg KH <gregkh@suse.de>
To: Daniel Mack <daniel@caiaq.de>
Cc: Eric Miao <eric.y.miao@gmail.com>,
Jakob Viketoft <jakob.viketoft@bitsim.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] colibri.h: Fix building for colibri 270...
Date: Wed, 5 May 2010 09:15:53 -0700 [thread overview]
Message-ID: <20100505161553.GA8462@suse.de> (raw)
In-Reply-To: <20100505155424.GL30801@buzzloop.caiaq.de>
On Wed, May 05, 2010 at 05:54:24PM +0200, Daniel Mack wrote:
> On Wed, May 05, 2010 at 08:20:00AM -0700, Greg KH wrote:
> > On Wed, May 05, 2010 at 11:44:05AM +0200, Daniel Mack wrote:
> > > On Wed, May 05, 2010 at 05:28:45PM +0800, Eric Miao wrote:
> > > > On Wed, May 5, 2010 at 4:00 PM, Daniel Mack <daniel@caiaq.de> wrote:
> > > > > On Wed, May 05, 2010 at 03:45:34PM +0800, Eric Miao wrote:
> > > > >> On Fri, Apr 16, 2010 at 7:29 PM, Daniel Mack <daniel@caiaq.de> wrote:
> > > > >> > On Fri, Apr 16, 2010 at 01:28:20PM +0200, Daniel Mack wrote:
> > > > >> >> On Fri, Apr 16, 2010 at 01:25:49PM +0200, Jakob Viketoft wrote:
> > > > >> >> > Adding a "#include <mach/mfp.h>" seem to cure this problem. If you
> > > > >> >> > agree I can supply a new patch with the correct solution this time.
> > > > >> >>
> > > > >> >> Ok. Add it to colibri.h, and while at it, you can kick the ax88796.h
> > > > >> >> inclusion. That's a leftover and isn't needed.
> > > > >> >
> > > > >> > And Cc: stable@kernel.org for the backmerge to 2.6.33.
> > > > >> >
> > > > >>
> > > > >> Jakob, any update on this?
> > > > >
> > > > > Jakob provided an updated patch for this:
> > > > >
> > > > > http://lkml.org/lkml/2010/4/16/100
> > > > >
> > > >
> > > > Looks it didn't make into -stable.
> > >
> > > Greg, stable@kernel.org was in Cc: for the patch in the URL above.
> > > Any chance to get this in?
> >
> > Is it in Linus's tree? If so, what is the git commit id of it? If you
> > properly tag the patch with "cc: stable <stable@kernel.org>" like you
> > did in the patch, then it will be automatically sent to me when it hits
> > Linus's tree.
>
> I see - thought you were picking them up from the mails.
> Thanks for explaining :)
>
> > I don't see this one in my queue at the moment.
>
> It's not there yet. Eric picked it, but I'm not sure whether it will
> still make it to .34. But ok, let's just wait then.
I _CAN_NOT_ take patches into the stable tree before they go into
Linus's tree, so even if I was picking them up from emails, this could
not be accepted.
Please read the file, Documentation/stable_kernel_rules.txt for how the
process works.
thanks,
greg k-h
next prev parent reply other threads:[~2010-05-05 16:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 9:51 [PATCH] colibri.h: Fix building for colibri 270 Jakob Viketoft
2010-04-16 10:01 ` Daniel Mack
2010-04-16 11:17 ` Jakob Viketoft
2010-04-16 11:25 ` Jakob Viketoft
2010-04-16 11:28 ` Daniel Mack
2010-04-16 11:29 ` Daniel Mack
2010-05-05 7:45 ` Eric Miao
2010-05-05 8:00 ` Daniel Mack
2010-05-05 9:28 ` Eric Miao
2010-05-05 9:44 ` Daniel Mack
2010-05-05 9:47 ` Eric Miao
2010-05-05 9:53 ` Daniel Mack
2010-05-05 10:21 ` Eric Miao
2010-05-05 11:02 ` Jakob Viketoft
2010-05-05 15:20 ` Greg KH
2010-05-05 15:54 ` Daniel Mack
2010-05-05 16:15 ` Greg KH [this message]
2010-04-16 11:26 ` Daniel Mack
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=20100505161553.GA8462@suse.de \
--to=gregkh@suse.de \
--cc=daniel@caiaq.de \
--cc=eric.y.miao@gmail.com \
--cc=jakob.viketoft@bitsim.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox