From: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Normal service will resume shortly ...
Date: Tue, 17 Jan 2017 14:41:48 +0530 [thread overview]
Message-ID: <587DDFD4.1010204@linux.vnet.ibm.com> (raw)
In-Reply-To: <87pojncpt6.fsf@concordia.ellerman.id.au>
Hi Michael,
Welcome back!!
Can you please take a look at:
https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-November/151426.html
https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-November/150452.html
Thanks,
Ravi
On Monday 16 January 2017 03:03 PM, Michael Ellerman wrote:
> Hi folks,
>
> I'm back from paternity leave, and will start processing patches in the
> next day or two.
>
> If you've sent a fix that should go into 4.10 that hasn't been merged
> yet, please feel free to reply to this message giving me a pointer to
> it.
>
> cheers
>
next prev parent reply other threads:[~2017-01-17 9:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 9:33 Normal service will resume shortly Michael Ellerman
2017-01-16 21:54 ` Reza Arbab
2017-01-16 23:01 ` Gavin Shan
2017-01-17 9:11 ` Ravi Bangoria [this message]
2017-01-17 17:02 ` Michael Bringmann
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=587DDFD4.1010204@linux.vnet.ibm.com \
--to=ravi.bangoria@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).