From: Denys Dmytriyenko <denis@denix.org>
To: Marek Vasut <marex@denx.de>
Cc: openembedded-core@lists.openembedded.org,
Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] u-boot: Update to 2017.03 release
Date: Wed, 29 Mar 2017 17:56:58 -0400 [thread overview]
Message-ID: <20170329215658.GP15664@denix.org> (raw)
In-Reply-To: <5c037512-7bf1-8a3c-cb76-fda7230781a0@denx.de>
On Mon, Mar 27, 2017 at 04:31:16PM +0200, Marek Vasut wrote:
> On 03/27/2017 04:25 PM, Richard Purdie wrote:
> > On Mon, 2017-03-27 at 16:22 +0200, Marek Vasut wrote:
> >> Upgrade U-Boot to the latest version.
> >
> > Wrong list and how does this compare to Ovatio's patch?
>
> I was not CCed on Otavio's patch :(
Yeah, me neither, unfortunately - people just ignore maintainers file now.
Good thing Ross copied me on the other discussion!
--
Denys
WARNING: multiple messages have this Message-ID (diff)
From: Denys Dmytriyenko <denis@denix.org>
To: Marek Vasut <marex@denx.de>
Cc: openembedded-core@lists.openembedded.org,
openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] u-boot: Update to 2017.03 release
Date: Wed, 29 Mar 2017 17:56:58 -0400 [thread overview]
Message-ID: <20170329215658.GP15664@denix.org> (raw)
In-Reply-To: <5c037512-7bf1-8a3c-cb76-fda7230781a0@denx.de>
On Mon, Mar 27, 2017 at 04:31:16PM +0200, Marek Vasut wrote:
> On 03/27/2017 04:25 PM, Richard Purdie wrote:
> > On Mon, 2017-03-27 at 16:22 +0200, Marek Vasut wrote:
> >> Upgrade U-Boot to the latest version.
> >
> > Wrong list and how does this compare to Ovatio's patch?
>
> I was not CCed on Otavio's patch :(
Yeah, me neither, unfortunately - people just ignore maintainers file now.
Good thing Ross copied me on the other discussion!
--
Denys
next prev parent reply other threads:[~2017-03-29 21:57 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 14:22 [PATCH] u-boot: Update to 2017.03 release Marek Vasut
2017-03-27 14:25 ` Richard Purdie
2017-03-27 14:31 ` Marek Vasut
2017-03-29 21:56 ` Denys Dmytriyenko [this message]
2017-03-29 21:56 ` Denys Dmytriyenko
2017-03-29 22:16 ` Richard Purdie
2017-03-29 23:00 ` Denys Dmytriyenko
2017-03-30 8:21 ` Marek Vasut
2017-03-30 8:21 ` Marek Vasut
2017-03-30 13:24 ` Denys Dmytriyenko
2017-03-30 13:24 ` Denys Dmytriyenko
2017-03-30 14:12 ` Marek Vasut
2017-03-30 14:12 ` Marek Vasut
2017-03-30 18:06 ` Denys Dmytriyenko
2017-03-30 18:06 ` Denys Dmytriyenko
2017-03-30 19:12 ` [OE-core] " Philip Balister
2017-03-30 19:12 ` Philip Balister
2017-03-30 19:26 ` [OE-core] " Otavio Salvador
2017-03-30 19:26 ` Otavio Salvador
2017-03-31 11:55 ` Burton, Ross
2017-03-31 11:55 ` Burton, Ross
-- strict thread matches above, loose matches on Subject: below --
2017-03-27 14:32 Marek Vasut
2017-03-28 11:07 ` Philip Balister
2017-03-26 20:08 Otavio Salvador
2017-03-26 21:14 ` Denys Dmytriyenko
2017-03-27 13:19 ` Otavio Salvador
2017-03-27 13:19 ` Burton, Ross
2017-03-27 13:28 ` Otavio Salvador
2017-03-27 15:47 ` Denys Dmytriyenko
2017-03-27 15:52 ` Burton, Ross
2017-03-27 17:49 ` Denys Dmytriyenko
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=20170329215658.GP15664@denix.org \
--to=denis@denix.org \
--cc=marex@denx.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.