From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] lib: div64: sync with Linux
Date: Thu, 6 Apr 2017 08:45:03 -0400 [thread overview]
Message-ID: <20170406124503.GH19897@bill-the-cat> (raw)
In-Reply-To: <20170406060442.GA20622@linux-7smt.suse>
On Thu, Apr 06, 2017 at 02:04:44PM +0800, Peng Fan wrote:
> Hi Tom,
>
> On Wed, Apr 05, 2017 at 09:32:51AM -0400, Tom Rini wrote:
> >On Tue, Mar 28, 2017 at 05:05:09PM +0800, Peng Fan wrote:
> >
> >> Sync with Linux commit ad0376eb1483b ("Merge tag 'edac_for_4.11_2'").
> >>
> >> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> >> Cc: Tom Rini <trini@konsulko.com>
> >> ---
> >> include/linux/math64.h | 172 +++++++++++++++++++++++++++++++++++++++++++++++++
> >> lib/div64.c | 141 ++++++++++++++++++++++++++++++++++++++--
> >> 2 files changed, 308 insertions(+), 5 deletions(-)
> >
> >This seems fine. What would help would be a link to a travis-ci job
> >with this particular patch applied showing everything still builds too
> >:) Thanks!
>
> Do you mean I need to put a travis-ci job link in the commit log?
> I just use buildman to do the build on my local PC, I do not have
> travis-ci building.
Below the '---' is better probably. Did you buildman everything or just
arm/powerpc? Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170406/ac117919/attachment.sig>
next prev parent reply other threads:[~2017-04-06 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 9:05 [U-Boot] [PATCH] lib: div64: sync with Linux Peng Fan
2017-04-05 13:32 ` Tom Rini
2017-04-06 6:04 ` Peng Fan
2017-04-06 12:45 ` Tom Rini [this message]
2017-04-07 15:51 ` [U-Boot] " Tom Rini
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=20170406124503.GH19897@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