public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Allwinner fixes for v4.19 - Round 2
Date: Sun, 23 Sep 2018 05:32:57 -0700	[thread overview]
Message-ID: <20180923123257.kk5g5xd2tjbsurfj@localhost> (raw)
In-Reply-To: <20180920042453.GA18194@wens.csie.org>

On Thu, Sep 20, 2018 at 12:24:53PM +0800, Chen-Yu Tsai wrote:
> Hi,
> 
> This is a second fixes pull request for arm-soc, based on the first pull
> request I sent earlier.
> 
> Also, I seem to remember seeing on ksummit-discuss that single patch PRs
> are a bit annoying. Would the maintainers prefer we just resend single
> patches instead? I'm not sure how that would work out if we later had
> to base -next material on it, but I guess we could base it off a -fixes
> branch in arm-soc.

Either base it off of our fixes branch, or if the fix goes into an early -rc
you can also based it off of that (but we try to avoid moving forward onto
later rcs if we can).

Single patch pull requests are OK as well. Whatever fits your workflow the
best, but if sending patches works, feel free to.

> The following changes since commit d177c8b61d6b4ef360b1c2682e4d8e3bae01738b:
> 
>   arm64: allwinner: dts: h6: fix Pine H64 MMC bus width (2018-08-27 09:21:00 +0200)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git tags/sunxi-fixes-for-4.19-2

Merged, thanks.


-Olof

      reply	other threads:[~2018-09-23 12:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-20  4:24 [GIT PULL] Allwinner fixes for v4.19 - Round 2 Chen-Yu Tsai
2018-09-23 12:32 ` Olof Johansson [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=20180923123257.kk5g5xd2tjbsurfj@localhost \
    --to=olof@lixom.net \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox