public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Jochen Friedrich <jochen@scram•de>
To: Scott Wood <scottwood@freescale•com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs•org>,
	Paul Mackerras <paulus@samba•org>
Subject: Re: Please pull from 'for-2.6.27'
Date: Thu, 25 Sep 2008 10:50:44 +0200	[thread overview]
Message-ID: <48DB50E4.4050509@scram.de> (raw)
In-Reply-To: <20080924224347.GA29132@ld0162-tx32.am.freescale.net>

Hi Scott,

>> This isn't a regression since the stuff is new in 2.6.27. IMHO this can
>> wait until 2.6.28.
> 
> It would be a bug in 2.6.27 that did not exist in 2.6.26...  is there
> anything that used to use another mechanism that now uses this?

No, GPIO support on CPM1/CPM2 is new in 2.6.27. Before, dedicated platform 
drivers were needed to drive hardware connected to an GPIO pin.

> That's not to say that it's necessarily critical enough this late in the
> process, but in general I'm not very comfortable with not being able to
> fix newly added code as soon as the merge window closes because it's not
> a "regression".

If i understood Linus correctly, this fix will have to wait for 2.6.28, but
then it can also enter the 2.6.27 stable series (like 2.6.27.1).

Thanks,
Jochen

      reply	other threads:[~2008-09-25  8:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-12 20:47 Please pull from 'for-2.6.27' Kumar Gala
2008-09-16 14:53 ` Kumar Gala
2008-09-16 17:48   ` Paul Mackerras
2008-09-16 18:41     ` Kumar Gala
2008-09-17 10:29     ` Jochen Friedrich
2008-09-24 22:43       ` Scott Wood
2008-09-25  8:50         ` Jochen Friedrich [this message]

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=48DB50E4.4050509@scram.de \
    --to=jochen@scram$(echo .)de \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=paulus@samba$(echo .)org \
    --cc=scottwood@freescale$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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