public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Baolin Wang <baolin.wang@linaro.org>
Cc: arnd@arndb.de, john.stultz@linaro.org, heenasirwani@gmail.com,
	pang.xunlei@linaro.org, peterz@infradead.org,
	rafael.j.wysocki@intel.com, gregkh@linuxfoundation.org,
	richardcochran@gmail.com, benh@kernel.crashing.org,
	paulus@samba.org, mpe@ellerman.id.au, schwidefsky@de.ibm.com,
	heiko.carstens@de.ibm.com, linux390@de.ibm.com, rth@twiddle.net,
	riel@redhat.com, cl@linux.com, tj@kernel.org, fweisbec@gmail.com,
	ahh@google.com, pjt@google.com, linuxppc-dev@lists.ozlabs.org,
	linux-s390@vger.kernel.org, linux-arch@vger.kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	serge.hallyn@canonical.com, james.l.morris@oracle.com,
	serge@hallyn.com, pmoore@redhat.com, tiwai@suse.de,
	jeffv@google.com, jlayton@primarydata.com, keescook@chromium.org,
	sds@tycho.nsa.gov, mark.d.rustad@intel.com,
	linux-security-module@vger.kernel.org, y2038@lists.linaro.org
Subject: Re: [PATCH v4 00/25] Convert the posix_clock_operations and k_clock structure to ready for 2038
Date: Tue, 2 Jun 2015 21:19:17 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.11.1506021719290.20347@nanos> (raw)
Message-ID: <20150602191917.CmFBLyMHvIDWRveiZ9fjG8FdKbX3U9XQ7MZL4YWqUYs@z> (raw)
In-Reply-To: <1433159093-4548-1-git-send-email-baolin.wang@linaro.org>

On Mon, 1 Jun 2015, Baolin Wang wrote:

You failed to thread the patch series again ....

  reply	other threads:[~2015-06-02 19:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150601114453.9cJVfkk16ekR6p5JE4iB1Tlozy1rfsmhxysxjqJ5Djs@z>
2015-06-01 11:44 ` [PATCH v4 00/25] Convert the posix_clock_operations and k_clock structure to ready for 2038 Baolin Wang
     [not found]   ` <20150602191917.CmFBLyMHvIDWRveiZ9fjG8FdKbX3U9XQ7MZL4YWqUYs@z>
2015-06-02 19:19     ` Thomas Gleixner [this message]
2015-06-02 19:20   ` Thomas Gleixner
2015-06-03  2:13     ` Baolin Wang

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=alpine.DEB.2.11.1506021719290.20347@nanos \
    --to=tglx@linutronix.de \
    --cc=ahh@google.com \
    --cc=arnd@arndb.de \
    --cc=baolin.wang@linaro.org \
    --cc=benh@kernel.crashing.org \
    --cc=cl@linux.com \
    --cc=fweisbec@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heenasirwani@gmail.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=james.l.morris@oracle.com \
    --cc=jeffv@google.com \
    --cc=jlayton@primarydata.com \
    --cc=john.stultz@linaro.org \
    --cc=keescook@chromium.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=linux390@de.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mark.d.rustad@intel.com \
    --cc=mpe@ellerman.id.au \
    --cc=netdev@vger.kernel.org \
    --cc=pang.xunlei@linaro.org \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=pjt@google.com \
    --cc=pmoore@redhat.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=richardcochran@gmail.com \
    --cc=riel@redhat.com \
    --cc=rth@twiddle.net \
    --cc=schwidefsky@de.ibm.com \
    --cc=sds@tycho.nsa.gov \
    --cc=serge.hallyn@canonical.com \
    --cc=serge@hallyn.com \
    --cc=tiwai@suse.de \
    --cc=tj@kernel.org \
    --cc=y2038@lists.linaro.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