All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ixp4xx: fix compilation by adding gpiolib support
Date: Wed, 23 May 2012 19:39:49 +0000	[thread overview]
Message-ID: <201205231939.49681.arnd@arndb.de> (raw)
In-Reply-To: <87396qbtrx.fsf@lebrac.rtp-net.org>

On Wednesday 23 May 2012, Arnaud Patard wrote:
> Arnd Bergmann <arnd@arndb.de> writes:
> 
> > On Wednesday 23 May 2012, Richard Cochran wrote:
> >> Once again, ixp4xx no longer even compiles. This patch fixes the issue
> >> by converting over to gpiolib. This patch was first made by Imre and
> >> posted by Marc, and I added in Russell's suggestion to empty the gpio
> >> header file.
> >> 
> >> This fix should also go for 3.1, 3.2, 3.3, and 3.4.
> >> 
> >> Signed-off-by: Richard Cochran <richardcochran@gmail.com>
> >> Cc: <stable@vger.kernel.org>
> >
> > So has every kernel since 3.1 been broken, or is it just broken now
> > but a good idea to backport anyway?
> 
> every kernel since 3.1 (even 3.1-rc-something). Would be nice to see
> this issue fixed as similar patches have been sent from time to time but
> never been merged.

Ok, thanks for the info. I'm sorry that it has come so far. I think Olof
and I are generally doing a good job at picking up all the pull requests,
but we sometimes miss single patches, especially when it's not clear that
they are expected to go into the arm-soc tree.

I have to admit that I didn't even remember who maintains ixp4xx, since
there hasn't been a single ixp4xx patch from Imre or Krzysztof that I've put
into the kernel over this time frame.

I've put the patch into the fixes branch now, it should be part of 
the next round of submissions.

What is the plan for ixp4xx going forward? Is one of you planning to
maintain a git tree and collect patches for inclusion in arm-soc?
I would be more comfortable just knowing where to pull from than
having to watch the mailing list and making sure the maintainers
Ack all the patches.
If there is no tree, should we downgrade ixp4xx in the MAINTAINERS
file from "Maintained" to "Odd fixes"?

	Arnd

  reply	other threads:[~2012-05-23 19:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-23 16:19 [PATCH] ixp4xx: fix compilation by adding gpiolib support Richard Cochran
2012-05-23 17:27 ` Jonathan Nieder
2012-05-23 18:18   ` Jonathan Nieder
2012-05-24  7:10     ` Richard Cochran
2012-05-23 17:43 ` Arnd Bergmann
2012-05-23 19:07   ` Arnaud Patard (Rtp)
2012-05-23 19:39     ` Arnd Bergmann [this message]
2012-05-24  7:07       ` Richard Cochran
2012-05-24  9:01         ` Arnd Bergmann
2012-05-24 10:16           ` Richard Cochran
2012-05-24  9:31       ` Imre Kaloz
2012-05-24 13:12         ` Arnd Bergmann
2012-05-24 15:13           ` Richard Cochran
2012-05-27 20:52     ` Krzysztof Halasa
2012-05-28  5:43       ` Richard Cochran

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=201205231939.49681.arnd@arndb.de \
    --to=arnd@arndb.de \
    --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.