From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Olof Johansson <olof@lixom.net>,
arm@kernel.org, Russell King <linux@arm.linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] ARM: uniphier: UniPhier updates for Linux 4.6-rc1 (2nd round)
Date: Mon, 21 Mar 2016 20:33:21 +0100 [thread overview]
Message-ID: <9542345.80KhJJ4ttZ@wuerfel> (raw)
In-Reply-To: <CAK7LNAR_=p4phcse7oS0xjJsVhZ_jZ36su0zYT3LynwYH1jABw@mail.gmail.com>
On Monday 21 March 2016 21:39:31 Masahiro Yamada wrote:
> Hi Arnd,
>
> 2016-03-21 18:49 GMT+09:00 Arnd Bergmann <arnd@arndb.de>:
> > On Monday 21 March 2016 12:59:20 Masahiro Yamada wrote:
> >>
> >> I thought you'd include DT updates in the pull requests,
> >> but you didn't.
> >>
> >> Why was next/dt2 missed?
> >
> > This is the branch that I pulled in some patches last, I'm going to send
> > it in a couple of days, after it has been in linux-next. It should be there
> > in the end.
>
> I did not know this.
> That'll be great.
>
> Sorry for poking you again and again.
Nothing wrong on your end. Generally it's a good idea to remind us if you
send patches and nothing happens after a week, or you are unsure whether
we actually did what we said we'd do (as in this case).
I should really have been clearer in the pull request message about the
fact that there is still some part missing.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: uniphier: UniPhier updates for Linux 4.6-rc1 (2nd round)
Date: Mon, 21 Mar 2016 20:33:21 +0100 [thread overview]
Message-ID: <9542345.80KhJJ4ttZ@wuerfel> (raw)
In-Reply-To: <CAK7LNAR_=p4phcse7oS0xjJsVhZ_jZ36su0zYT3LynwYH1jABw@mail.gmail.com>
On Monday 21 March 2016 21:39:31 Masahiro Yamada wrote:
> Hi Arnd,
>
> 2016-03-21 18:49 GMT+09:00 Arnd Bergmann <arnd@arndb.de>:
> > On Monday 21 March 2016 12:59:20 Masahiro Yamada wrote:
> >>
> >> I thought you'd include DT updates in the pull requests,
> >> but you didn't.
> >>
> >> Why was next/dt2 missed?
> >
> > This is the branch that I pulled in some patches last, I'm going to send
> > it in a couple of days, after it has been in linux-next. It should be there
> > in the end.
>
> I did not know this.
> That'll be great.
>
> Sorry for poking you again and again.
Nothing wrong on your end. Generally it's a good idea to remind us if you
send patches and nothing happens after a week, or you are unsure whether
we actually did what we said we'd do (as in this case).
I should really have been clearer in the pull request message about the
fact that there is still some part missing.
Arnd
next prev parent reply other threads:[~2016-03-21 19:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 7:16 [PATCH 0/2] ARM: uniphier: UniPhier updates for Linux 4.6-rc1 (2nd round) Masahiro Yamada
2016-02-26 7:16 ` Masahiro Yamada
2016-02-26 7:16 ` [PATCH 1/2] ARM: uniphier: add missing of_node_put() Masahiro Yamada
2016-02-26 7:16 ` Masahiro Yamada
2016-02-26 7:16 ` [PATCH 2/2] ARM: uniphier: rework SMP code to support new System Bus binding Masahiro Yamada
2016-02-26 7:16 ` Masahiro Yamada
2016-03-07 9:30 ` [PATCH 0/2] ARM: uniphier: UniPhier updates for Linux 4.6-rc1 (2nd round) Masahiro Yamada
2016-03-07 9:30 ` Masahiro Yamada
2016-03-12 23:42 ` Masahiro Yamada
2016-03-12 23:42 ` Masahiro Yamada
2016-03-15 2:01 ` Masahiro Yamada
2016-03-15 2:01 ` Masahiro Yamada
2016-03-18 16:49 ` Arnd Bergmann
2016-03-18 16:49 ` Arnd Bergmann
2016-03-18 23:49 ` Masahiro Yamada
2016-03-18 23:49 ` Masahiro Yamada
2016-03-21 3:59 ` Masahiro Yamada
2016-03-21 3:59 ` Masahiro Yamada
2016-03-21 9:49 ` Arnd Bergmann
2016-03-21 9:49 ` Arnd Bergmann
2016-03-21 12:39 ` Masahiro Yamada
2016-03-21 12:39 ` Masahiro Yamada
2016-03-21 19:33 ` Arnd Bergmann [this message]
2016-03-21 19:33 ` Arnd Bergmann
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=9542345.80KhJJ4ttZ@wuerfel \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=yamada.masahiro@socionext.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.