All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kieran Bingham <kieran@ksquared.org.uk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	corbet@lwn.net, osandov@fb.com, n.borisov.lkml@gmail.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] scripts/gdb: Fixes for 4.7
Date: Mon, 11 Jul 2016 21:15:07 +0100	[thread overview]
Message-ID: <5783FE4B.8070006@bingham.xyz> (raw)
In-Reply-To: <20160711125316.61167a973e360eb73a7ebf48@linux-foundation.org>

On 11/07/16 20:53, Andrew Morton wrote:
> On Mon, 11 Jul 2016 11:17:21 +0100 Kieran Bingham <kieran@ksquared.org.uk> wrote:
> 
>> Will this fixes series be able to make it for 4.7 ?
> 
> Yup, I'll send them in this week.  Sorry, I've been a bit laggy the
> past two weeks.  Back up to speed now though.

No Worries, I saw you'd only sent about 2 emails in the last two weeks
and thought you might have been on holiday.

Then I saw Linus' rc notes, and saw we get an extra week as well!

Thanks
-- 
Regards

Kieran Bingham

      reply	other threads:[~2016-07-11 20:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28 15:22 [PATCH 0/6] scripts/gdb: Fixes for 4.7 Kieran Bingham
2016-06-28 15:22 ` [PATCH 1/6] scripts/gdb: silence 'nothing to do' message Kieran Bingham
2016-06-28 15:22 ` [PATCH 2/6] scripts/gdb: rebuild constants.py on dependancy change Kieran Bingham
2016-06-28 15:22 ` [PATCH 3/6] scripts/gdb: add constants.py to .gitignore Kieran Bingham
2016-06-28 15:22 ` [PATCH 4/6] scripts/gdb: Perform path expansion to lx-symbol's arguments Kieran Bingham
2016-06-28 15:22 ` [PATCH 5/6] Revert "scripts/gdb: add a Radix Tree Parser" Kieran Bingham
2016-06-28 15:22 ` [PATCH 6/6] Revert "scripts/gdb: add documentation example for radix tree" Kieran Bingham
2016-06-29  5:00 ` [PATCH 0/6] scripts/gdb: Fixes for 4.7 Jan Kiszka
2016-07-11 10:17   ` Kieran Bingham
2016-07-11 19:53     ` Andrew Morton
2016-07-11 20:15       ` Kieran Bingham [this message]

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=5783FE4B.8070006@bingham.xyz \
    --to=kieran@ksquared.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=jan.kiszka@siemens.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=n.borisov.lkml@gmail.com \
    --cc=osandov@fb.com \
    /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.