From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: Patches pending for review
Date: Tue, 16 Mar 2021 18:26:49 -0400 [thread overview]
Message-ID: <20210316222649.GD1310@bill-the-cat> (raw)
In-Reply-To: <d9af329c1b616a843e299255be0a129176c6a7e1.camel@gmail.com>
On Tue, Mar 16, 2021 at 11:24:10PM +0100, Daniel Schwierzeck wrote:
> Am Montag, den 15.03.2021, 21:24 +0000 schrieb Aleksandar Gerasimovski:
> > Hi Folks,
> >
> > Hope you are all well!
> >
> > I guess you have verry busy times, but I have to ask about the state
> > of my last two patches on patchwork:
> >
> > https://patchwork.ozlabs.org/project/uboot/patch/VI1PR06MB402989C0EFEE6A5121437C68D2819 at VI1PR06MB4029.eurprd06.prod.outlook.com/
> > https://patchwork.ozlabs.org/project/uboot/patch/VI1PR06MB40297747EE7A342B4D3F0E2FD2819 at VI1PR06MB4029.eurprd06.prod.outlook.com/
> >
> > They are in same state since almost a month, and for me it looks like
> > they are forgotten.
> > Is it possible to get attention from some of you? Thanks in advance!
>
> I don't know why the patches were assigned to me and who did that. Also
> the patches were in state "Changes requested" so they were not visible
> in my patchwork inbox. Maybe someone's patchwork script went crazy ;)
>
> I've reassigned the patches to Priyanka who is NXP maintainer and
> changed the state to "New". Hope this helps ;)
Lets just assume I typo'd somewhere along the line, sorry about that.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20210316/a7a8ea49/attachment.sig>
next prev parent reply other threads:[~2021-03-16 22:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 21:24 Patches pending for review Aleksandar Gerasimovski
2021-03-16 22:24 ` Daniel Schwierzeck
2021-03-16 22:26 ` Tom Rini [this message]
2021-03-24 4:42 ` Priyanka Jain
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=20210316222649.GD1310@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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