From: Paul Mundt <lethal@linux-sh.org>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] SuperHyway bus support
Date: Wed, 2 Feb 2005 09:04:43 +0200 [thread overview]
Message-ID: <20050202070443.GA25641@linux-sh.org> (raw)
In-Reply-To: <20050201223008.GA14331@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]
On Tue, Feb 01, 2005 at 02:30:08PM -0800, Greg KH wrote:
> On Tue, Feb 01, 2005 at 11:23:27PM +0100, Sam Ravnborg wrote:
> > On Tue, Feb 01, 2005 at 02:05:52PM -0800, Greg KH wrote:
> > > > drivers/sh/Makefile | 6
> > > > drivers/sh/superhyway/Makefile | 7 +
> > > > drivers/sh/superhyway/superhyway-sysfs.c | 45 ++++++
> > > > drivers/sh/superhyway/superhyway.c | 201 +++++++++++++++++++++++++++++++
> > > > include/linux/superhyway.h | 79 ++++++++++++
> > > > 5 files changed, 338 insertions(+)
> >
> > Why does it need a .h file in include/linux/?
> > Only use include/linux/* for .h files which is used by other parts of
> > the kernel.
> >
> > [I've lost the original mail - so cannot see the actual source].
>
> Other parts of the kernel will use that .h file when they register
> themselves with the sh bus. Right Paul?
>
Yes, that's correct. Any driver with a SuperHyway device will need it,
and this will be on multiple architectures (sh and sh64).
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-02-02 7:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 7:52 [PATCH] SuperHyway bus support Paul Mundt
2005-01-07 7:22 ` Greg KH
2005-01-07 9:41 ` Paul Mundt
2005-01-07 16:29 ` Paul Mundt
2005-01-12 8:17 ` Greg KH
2005-01-12 12:48 ` Paul Mundt
2005-01-25 14:08 ` Paul Mundt
2005-01-25 20:30 ` Greg KH
2005-02-01 22:05 ` Greg KH
2005-02-01 22:23 ` Sam Ravnborg
2005-02-01 22:30 ` Greg KH
2005-02-02 7:04 ` Paul Mundt [this message]
2005-02-02 7:10 ` Paul Mundt
2005-02-02 22:19 ` Greg KH
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=20050202070443.GA25641@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=greg@kroah.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