From: Paul Mundt <lethal@linux-sh.org>
To: Adrian McMenamin <adrian@newgolddream.dyndns.info>,
Adrian McMenamin <lkmladrian@gmail.com>
Cc: linux-sh <linuxsh-dev@lists.sourceforge.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix maple bus compiler warning
Date: Tue, 30 Oct 2007 09:51:07 +0900 [thread overview]
Message-ID: <20071030005107.GD13661@linux-sh.org> (raw)
In-Reply-To: <8b67d60710280724s761f1d29t9de57941a9800913@mail.gmail.com> <1193530224.6094.9.camel@localhost.localdomain>
On Sun, Oct 28, 2007 at 02:24:10PM +0000, Adrian McMenamin wrote:
> The API for uevent has changed for 2.6.24 and this patch makes a
> consequential clean up.
>
> (Apols to linux-sh list users seeing this for the second time, I
> should have included lkml first time round for completeness)
>
> Signed-off-by: Adrian McMenamin <adrian@mcmen.demon.co.uk>
>
Applied, thanks.
prev parent reply other threads:[~2007-10-30 1:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-28 14:24 [PATCH - SH] Clean up maple bus code to supress compiler warning Adrian McMenamin
[not found] ` <1193530224.6094.9.camel@localhost.localdomain>
2007-10-30 0:51 ` Paul Mundt [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=20071030005107.GD13661@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=adrian@newgolddream.dyndns.info \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxsh-dev@lists.sourceforge.net \
--cc=lkmladrian@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 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.