linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: slash.tmp@free.fr (Mason)
To: linux-arm-kernel@lists.infradead.org
Subject: IRQ setup on multicore systems (routing, balancing, etc)
Date: Thu, 06 Aug 2015 17:17:06 +0200	[thread overview]
Message-ID: <55C37A72.2090507@free.fr> (raw)
In-Reply-To: <55C0C102.7050600@free.fr>

On 04/08/2015 15:41, Mason wrote:

> I have a few very naive questions about [snip]

[META]

Are there perhaps more suitable mailing lists than this one
for such beginner questions?

(It looks like LAKML is for experienced Linux devs proposing kernel
changes, or submitting patches for existing ports.)

I lurked in the #devicetree IRC channel, but there was no activity
in ~6 hours (despite 40 people connected).

Hmmm, I'll give kernelnewbies a try.
http://kernelnewbies.org/mailinglistguidelines

Regards.

  parent reply	other threads:[~2015-08-06 15:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04 13:41 IRQ setup on multicore systems (routing, balancing, etc) Mason
2015-08-05  8:40 ` Mason
2015-08-06 15:17 ` Mason [this message]
2015-08-06 15:26   ` Russell King - ARM Linux
2015-08-06 16:14     ` Mason
2015-08-06 20:38       ` Russell King - ARM Linux

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=55C37A72.2090507@free.fr \
    --to=slash.tmp@free.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).