All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Dinh Nguyen <dinguyen@kernel.org>
Cc: ARM-SoC Maintainers <arm@kernel.org>, SoC Team <soc@kernel.org>
Subject: Re: [GIT PULL] ARM: socfpga: fix for v5.16, part 3
Date: Wed, 5 Jan 2022 16:23:00 -0800	[thread overview]
Message-ID: <CAOesGMj7y6z6p_vMUVaPbSuieZBhHqk=L9MC+yx8UwK2T+coog@mail.gmail.com> (raw)
In-Reply-To: <20211227103644.566694-1-dinguyen@kernel.org>

Hi Dinh,

On Mon, Dec 27, 2021 at 2:36 AM Dinh Nguyen <dinguyen@kernel.org> wrote:
>
> Hi Arnd/Olof,
>
> Please pull in these 2 patches for v5.16. The reason for this dts compatible
> change is that the commit 98d948eb833 ("spi: cadence-quadspi: fix write
> completion support") is already part of v5.16, thus we need these 2 patches to
> be in v5.16.
>
> Thanks,
> Dinh
>
> The following changes since commit fc74e0a40e4f9fd0468e34045b0c45bba11dcbb2:
>
>   Linux 5.16-rc7 (2021-12-26 13:17:17 -0800)

Was there a reason you chose to base this fixes branch on 5.16-rc7
instead of an older -rc, or the previous fixes branch that you sent
in?

As a result, we now have to bring the base version forward for our
fixes branch in our tree (and our for-next branch as well).

It's usually best practices to use an older -rc (-rc1/-rc2 if you
can), and/or continue using the same fixes branch if you have
dependencies between previous fixes sent in for this release cycle.

> are available in the Git repository at:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git tags/socfpga_fix_for_v5.16_part_3
>
> for you to fetch changes up to 36de991e93908f7ad5c2a0eac9c4ecf8b723fa4a:
>
>   ARM: dts: socfpga: change qspi to "intel,socfpga-qspi" (2021-12-27 04:20:06 -0600)

Merged this time, but please try to use older base branches in the
future. Thanks.


-Olof

  reply	other threads:[~2022-01-06  0:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-27 10:36 [GIT PULL] ARM: socfpga: fix for v5.16, part 3 Dinh Nguyen
2022-01-06  0:23 ` Olof Johansson [this message]
2022-01-06  1:26   ` Dinh Nguyen
2022-01-06 19:40 ` patchwork-bot+linux-soc
2022-01-06 19:40 ` patchwork-bot+linux-soc

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='CAOesGMj7y6z6p_vMUVaPbSuieZBhHqk=L9MC+yx8UwK2T+coog@mail.gmail.com' \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=soc@kernel.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.