From: Ralf Baechle <ralf@linux-mips.org>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: linux-pcmcia@lists.infradead.org,
Sergei Shtylyov <sshtylyov@ru.mvista.com>,
linux-mips@linux-mips.org
Subject: Re: [PATCH 6/9] pcmcia: fix Alchemy warnings
Date: Fri, 13 Jun 2008 15:02:58 +0100 [thread overview]
Message-ID: <20080613140258.GE16344@linux-mips.org> (raw)
In-Reply-To: <1212183079-30505-6-git-send-email-linux@dominikbrodowski.net>
On Fri, May 30, 2008 at 11:31:16PM +0200, Dominik Brodowski wrote:
> Subject: [PATCH 6/9] pcmcia: fix Alchemy warnings
>
> From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
>
> Fix the following warnings:
>
> drivers/pcmcia/au1000_generic.c: In function `au1x00_pcmcia_socket_probe':
> drivers/pcmcia/au1000_generic.c:405: warning: integer constant is too large for
> "long" type
> drivers/pcmcia/au1000_generic.c:413: warning: integer constant is too large for
> "long" type
>
> by properly postfixing the socket constants. While at it, fix the lines over 80
> characters long in the vicinity...
>
> Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
> Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
> CC: linux-mips@linux-mips.org
Any reason why this patch still isn't merged? It looks right and seems to
do what it promised,
Acked-by: Ralf Baechle <ralf@linux-mips.org>
Ralf
next prev parent reply other threads:[~2008-06-13 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080530212821.GA30197@comet.dominikbrodowski.net>
2008-05-30 21:31 ` [PATCH 1/9] pcmcia: add an pata/ide ID Dominik Brodowski
2008-05-30 21:31 ` [PATCH 3/9] pcmcia: add another " Dominik Brodowski
2008-05-30 21:31 ` [PATCH 6/9] pcmcia: fix Alchemy warnings Dominik Brodowski
2008-05-30 21:31 ` Dominik Brodowski
2008-06-13 14:02 ` Ralf Baechle [this message]
2008-06-13 18:24 ` Dominik Brodowski
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=20080613140258.GE16344@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linux@dominikbrodowski.net \
--cc=sshtylyov@ru.mvista.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 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.