From: Andrew Jeffery <andrew@aj.id.au>
To: Christian Svensson <bluecmd@google.com>
Cc: "Christian Svensson" <blue@cmd.nu>,
"Cédric Le Goater" <clg@kaod.org>,
"openbmc @ lists . ozlabs . org" <openbmc@lists.ozlabs.org>,
"Joel Stanley" <joel@jms.id.au>
Subject: Re: [PATCH] qemu: aspeed_timer: Use signed muldiv for timer resets
Date: Tue, 12 Feb 2019 09:22:34 +1030 [thread overview]
Message-ID: <1549925554.1671710.1655910736.5D2C2BD2@webmail.messagingengine.com> (raw)
In-Reply-To: <CAEfeXvaYO4KRFYnsvfdEevzgNgCJTwY2EKsT6ow71hzK13HfMg@mail.gmail.com>
On Mon, 14 Jan 2019, at 17:48, Christian Svensson wrote:
> On Mon, Jan 14, 2019, 03:14 Andrew Jeffery <andrew@aj.id.au wrote:
>
> > On Fri, 11 Jan 2019, at 23:00, Christian Svensson wrote:
> > > Ping. What's left to be done here?
> >
> > I've taken Cedric's tree and pushed it to openbmc/qemu master, so the patch
> > is there. Did you send it upstream originally? That's where it should go,
> > but that
> > will probably require fixing the issue I pointed out last time.
> >
>
> Ah, wierd, I swore I checked the repository last week but I must have
> checked my own fork or something. Thanks for pulling the patch.
>
> As for fixing the issues, any specific concerns with the proposal I replied
> with back in November?
Sorry for the late reply here. What was the suggestion? I'll try to find the thread
in the mean time.
Andrew
prev parent reply other threads:[~2019-02-11 22:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 14:21 [PATCH] qemu: aspeed_timer: Use signed muldiv for timer resets Christian Svensson
2018-11-12 18:37 ` Cédric Le Goater
2018-11-12 18:45 ` Christian Svensson
2018-11-13 0:27 ` Andrew Jeffery
2018-11-13 8:58 ` Christian Svensson
2019-01-11 12:30 ` Christian Svensson
2019-01-14 2:14 ` Andrew Jeffery
2019-01-14 7:18 ` Christian Svensson
2019-02-11 22:52 ` Andrew Jeffery [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=1549925554.1671710.1655910736.5D2C2BD2@webmail.messagingengine.com \
--to=andrew@aj.id.au \
--cc=blue@cmd.nu \
--cc=bluecmd@google.com \
--cc=clg@kaod.org \
--cc=joel@jms.id.au \
--cc=openbmc@lists.ozlabs.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.