From: Christoph Hellwig <hch@infradead.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 2.6.11-rc2 1/1] altix: Device driver support for the CX port of SGI's TIO chip
Date: Tue, 15 Feb 2005 13:27:53 +0000 [thread overview]
Message-ID: <20050215132753.GA21988@infradead.org> (raw)
In-Reply-To: <20050211140321.20148.62620.40637@attica.americas.sgi.com>
> I tried to do that, for some reason the first patch (0/1) didn't make it
> to the mailing list. Is it important to separate the #include lines
> as well as the actual file moves?
In general we prefer to have separate patches for just moving things
around and real new functionality.
>
> > > DEFINE_PER_CPU(struct pda_s, pda_percpu);
> > > +EXPORT_PER_CPU_SYMBOL(pda_percpu);
> >
> > As mentioned the last time you posted it please use a proper accessor.
> >
>
> I don't understand what you want. The symbol is exported so that I can
> use existing macros from the tiocx code if it's built as a module.
What macros are that? You should probably just turn them into normal
functions unless they're performance-critical.
In fact I don't like the SGI pda at all - DEFINE_PER_CPU for each individual
member isn't anything less performant but much more managable. But
that's not a complaint to you but the core SGI plattform people.
> > With the above issues fixed it's fine to be queued up until you submit
> > an actual user of this interface.
> >
>
> I will work on providing an acceptable, meaningful, driver but it will
> take a bit. Would it be feasible for this code to go in now and for
> me to follow up with the driver later?
What users are this?
next prev parent reply other threads:[~2005-02-15 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 14:03 [PATCH 2.6.11-rc2 1/1] altix: Device driver support for the CX port of SGI's TIO chip Bruce Losure
2005-02-11 14:26 ` Christoph Hellwig
2005-02-11 20:40 ` [PATCH 2.6.11-rc2 1/1] altix: Device driver support for the CX Bruce Losure
2005-02-15 13:27 ` Christoph Hellwig [this message]
2005-02-15 15:45 ` Bruce Losure
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=20050215132753.GA21988@infradead.org \
--to=hch@infradead.org \
--cc=linux-ia64@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