From: Rik van Riel <riel@surriel.com>
To: sedat.dilek@gmail.com
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Davidlohr Bueso <davidlohr.bueso@hp.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
Paul McKenney <paul.mckenney@linaro.org>,
DRI <dri-devel@lists.freedesktop.org>,
Dave Airlie <airlied@redhat.com>,
Emmanuel Benisty <benisty.e@gmail.com>
Subject: Re: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
Date: Sat, 20 Apr 2013 11:59:40 -0400 [thread overview]
Message-ID: <5172BB6C.2020002@surriel.com> (raw)
In-Reply-To: <CA+icZUUG8bzGnnAhGfXA-gRRTin7cDj3-JK438PKepa=mgSJzw@mail.gmail.com>
On 04/20/2013 08:46 AM, Sedat Dilek wrote:
> I have started a new thread "[next-20130419] ipc: sem: BROKEN", please
> use this one!
>
> Thanks for all your feedback!
>
> - Sedat -
>
> [1] http://marc.info/?l=linux-next&m=136646172915261&w=2
I suspect most of us are not subscribed to the linux-next mailing list.
I know I'm not.
If you need someone on some email thread, you need to CC them on the
email.
--
All rights reversed.
WARNING: multiple messages have this Message-ID (diff)
From: Rik van Riel <riel@surriel.com>
To: sedat.dilek@gmail.com
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Davidlohr Bueso <davidlohr.bueso@hp.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
Paul McKenney <paul.mckenney@linaro.org>,
DRI <dri-devel@lists.freedesktop.org>,
Dave Airlie <airlied@redhat.com>,
Emmanuel Benisty <benisty.e@gmail.com>
Subject: Re: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
Date: Sat, 20 Apr 2013 11:59:40 -0400 [thread overview]
Message-ID: <5172BB6C.2020002@surriel.com> (raw)
In-Reply-To: <CA+icZUUG8bzGnnAhGfXA-gRRTin7cDj3-JK438PKepa=mgSJzw@mail.gmail.com>
On 04/20/2013 08:46 AM, Sedat Dilek wrote:
> I have started a new thread "[next-20130419] ipc: sem: BROKEN", please
> use this one!
>
> Thanks for all your feedback!
>
> - Sedat -
>
> [1] http://marc.info/?l=linux-next&m=136646172915261&w=2
I suspect most of us are not subscribed to the linux-next mailing list.
I know I'm not.
If you need someone on some email thread, you need to CC them on the
email.
--
All rights reversed.
next prev parent reply other threads:[~2013-04-20 15:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+icZUVWC+Rgd9wh4Z4CPZkEa9Pm2=2udnY5=UD1nnH0Wot1pQ@mail.gmail.com>
2013-04-18 19:48 ` linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ] Daniel Vetter
2013-04-18 21:59 ` Sedat Dilek
2013-04-19 10:19 ` Sedat Dilek
[not found] ` <CA+icZUXjTGSG+tejOAFgXr8EpKd7dL=-W41ha_-0N=roAxN3eg@mail.gmail.com>
2013-04-19 16:43 ` Sedat Dilek
2013-04-19 18:53 ` Sedat Dilek
2013-04-19 19:19 ` Rik van Riel
2013-04-19 20:12 ` Davidlohr Bueso
[not found] ` <CA+icZUVjx7pDJWo3tGxX3ANXtiTP0_Q1YyOowANhn1wzcSgWaA@mail.gmail.com>
2013-04-19 21:24 ` Linus Torvalds
2013-04-19 21:39 ` Paul E. McKenney
2013-04-19 22:12 ` Sedat Dilek
2013-04-19 22:34 ` Sedat Dilek
2013-04-19 22:50 ` Linus Torvalds
2013-04-19 22:55 ` Sedat Dilek
2013-04-19 23:02 ` Linus Torvalds
2013-04-19 23:02 ` Linus Torvalds
2013-04-20 0:06 ` Sedat Dilek
2013-04-20 0:19 ` Sedat Dilek
2013-04-20 12:46 ` Sedat Dilek
2013-04-20 15:59 ` Rik van Riel [this message]
2013-04-20 15:59 ` Rik van Riel
2013-04-20 17:04 ` Sedat Dilek
2013-04-20 20:00 ` Davidlohr Bueso
2013-04-20 21:03 ` Sedat Dilek
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=5172BB6C.2020002@surriel.com \
--to=riel@surriel.com \
--cc=airlied@redhat.com \
--cc=benisty.e@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=davidlohr.bueso@hp.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paul.mckenney@linaro.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@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 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.