linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@sifive.com>
To: Olof Johansson <olof@lixom.net>
Cc: aou@eecs.berkeley.edu, zongbox@gmail.com,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] RISC-V: A few build/warning fixes and cleanup
Date: Wed, 31 Oct 2018 10:09:07 -0700 (PDT)	[thread overview]
Message-ID: <mhng-74b51433-1762-4741-935d-56ca1b3548a0@palmer-si-x1c4> (raw)
In-Reply-To: <20181031064709.30981-1-olof@lixom.net>

On Tue, 30 Oct 2018 23:47:06 PDT (-0700), Olof Johansson wrote:
> A couple of fixes for build breakage or warnings, and a small whitespace/asm
> cleanup. The non-cleanups would be good to see in 4.20 to keep builds green.

I'm happy to just keep them all together, since the cleanups are non-functional 
changes.  Patch 1/3 appears to have disappeared from my inbox and I can't get 
to the infradead archives, do you mind re-sending it?

This also brings up a bigger issue: I need to stop breaking the build, 
particularly as we now support a bunch of configurations.  Is your CI stuff 
still running?  It'd be great to have it run against some of our integration 
branches so I can catch these before they make it upstream.  I haven't been 
getting any emails.

  parent reply	other threads:[~2018-10-31 17:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31  6:47 [PATCH 0/3] RISC-V: A few build/warning fixes and cleanup Olof Johansson
2018-10-31  6:47 ` [PATCH 1/3] RISC-V: lib: Fix build error for 64-bit Olof Johansson
2018-10-31  6:47 ` [PATCH 2/3] RISC-V: lib: minor asm cleanup Olof Johansson
2018-10-31  6:47 ` [PATCH 3/3] RISC-V: Silence some module warnings on 32-bit Olof Johansson
2018-10-31 17:09 ` Palmer Dabbelt [this message]
2018-10-31 17:52   ` [PATCH 0/3] RISC-V: A few build/warning fixes and cleanup Olof Johansson
2018-10-31 18:12     ` Logan Gunthorpe
2018-11-01  1:43       ` Fengguang Wu
2018-11-01  2:19         ` Li, Philip
2018-11-01 15:43           ` Logan Gunthorpe
2018-11-01 16:17             ` Palmer Dabbelt
2018-11-01 17:20               ` Olof Johansson

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=mhng-74b51433-1762-4741-935d-56ca1b3548a0@palmer-si-x1c4 \
    --to=palmer@sifive.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=olof@lixom.net \
    --cc=zongbox@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).