From: xerofoify@gmail.com (Nick Krause)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Delivery Status Notification (Failure)
Date: Wed, 6 Aug 2014 15:07:21 -0400 [thread overview]
Message-ID: <CAPDOMVgrhny6WwzyGterkiKNznwJqwjCcx8QgRXWFMniWKYmtQ@mail.gmail.com> (raw)
In-Reply-To: <20cf307f30f822dc1504fffa98ec@google.com>
Does anybody have some work in the scheduler subsystem I can work on
that is a good top dipping for a kernel newbie.
Regards Nick
next parent reply other threads:[~2014-08-06 19:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPDOMVhGTywBdA9W6cfE6bNb3CiM6Ei5rUi0OySO4dM3DbKX-w@mail.gmail.com>
[not found] ` <20cf307f30f822dc1504fffa98ec@google.com>
2014-08-06 19:07 ` Nick Krause [this message]
2014-08-06 19:29 ` Delivery Status Notification (Failure) Valdis.Kletnieks at vt.edu
2014-08-07 6:45 ` priyaranjan
2014-08-07 12:29 ` Pramod Gurav
2014-08-07 17:14 ` Nick Krause
2014-08-07 20:11 ` Valdis.Kletnieks at vt.edu
2014-08-07 20:33 ` Nick Krause
2015-03-23 5:27 Sysfs requirement for running generic_buffer.c application - IIO sensors s.rawat
[not found] ` <001a114904d6cd775e0511edee6f@google.com>
2015-03-23 5:44 ` Delivery Status Notification (Failure) s.rawat
-- strict thread matches above, loose matches on Subject: below --
2018-05-11 11:34 Not able to set smp_affinity for an IRQ on i.MX7 Pintu Kumar
[not found] ` <5af57fea.1c69fb81.885f0.2377.GMRIR@mx.google.com>
2018-05-11 11:37 ` Delivery Status Notification (Failure) Pintu Kumar
[not found] ` <20180511123915.GC16141@n2100.armlinux.org.uk>
2018-05-11 13:04 ` Lucas Stach
2018-05-11 14:37 ` Pintu Kumar
2018-05-14 12:12 ` Pintu Kumar
2018-05-14 13:11 ` Lucas Stach
2018-05-14 14:28 ` Pintu Kumar
2018-05-17 13:28 ` Pintu Kumar
2018-05-21 18:51 ` Pintu Kumar
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=CAPDOMVgrhny6WwzyGterkiKNznwJqwjCcx8QgRXWFMniWKYmtQ@mail.gmail.com \
--to=xerofoify@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).