From: gregkh@linuxfoundation.org (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: coresight: next v4.7-rc5
Date: Mon, 25 Jul 2016 13:36:30 -0700 [thread overview]
Message-ID: <20160725203630.GA1132@kroah.com> (raw)
In-Reply-To: <CANLsYkzsfq=f_rSBduM3Zy3rkxdVS5KfLnE18s8CFfEFfV2_eQ@mail.gmail.com>
On Mon, Jul 25, 2016 at 10:17:36AM -0600, Mathieu Poirier wrote:
> Good day Greg,
>
> A while back I sent a set of CoreSight related patches for you to
> consider for the 4.8 cycle. Since then I haven't received the usual
> set of emails telling me the patches have been added to your next
> tree. With the merge window now being open I was wondering if the
> patches have reached you and if you had the opportunity to look at
> them.
Yes, I got them, right on the day after I left for vacation, and I've
been traveling since :(
It missed 4.8, so unless these are bugfixes/regressions that need to get
into 4.8, I'll queue them up for 4.9. If they are things that should
get in, can you resend this as 2 series, one for 4.8 and one for 4.9?
thanks, and sorry about that.
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: coresight: next v4.7-rc5
Date: Mon, 25 Jul 2016 13:36:30 -0700 [thread overview]
Message-ID: <20160725203630.GA1132@kroah.com> (raw)
In-Reply-To: <CANLsYkzsfq=f_rSBduM3Zy3rkxdVS5KfLnE18s8CFfEFfV2_eQ@mail.gmail.com>
On Mon, Jul 25, 2016 at 10:17:36AM -0600, Mathieu Poirier wrote:
> Good day Greg,
>
> A while back I sent a set of CoreSight related patches for you to
> consider for the 4.8 cycle. Since then I haven't received the usual
> set of emails telling me the patches have been added to your next
> tree. With the merge window now being open I was wondering if the
> patches have reached you and if you had the opportunity to look at
> them.
Yes, I got them, right on the day after I left for vacation, and I've
been traveling since :(
It missed 4.8, so unless these are bugfixes/regressions that need to get
into 4.8, I'll queue them up for 4.9. If they are things that should
get in, can you resend this as 2 series, one for 4.8 and one for 4.9?
thanks, and sorry about that.
greg k-h
next prev parent reply other threads:[~2016-07-25 20:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 16:17 coresight: next v4.7-rc5 Mathieu Poirier
2016-07-25 16:17 ` Mathieu Poirier
2016-07-25 20:36 ` Greg KH [this message]
2016-07-25 20:36 ` Greg KH
2016-07-25 21:44 ` Mathieu Poirier
2016-07-25 21:44 ` Mathieu Poirier
2016-07-25 22:00 ` Greg KH
2016-07-25 22:00 ` Greg KH
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=20160725203630.GA1132@kroah.com \
--to=gregkh@linuxfoundation.org \
--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 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.