Linux-sh Archive mirror
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Oreoluwa Babatunde <quic_obabatun@quicinc.com>,
	 ysato@users.sourceforge.jp, dalias@libc.org
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
	robh+dt@kernel.org,  kernel@quicinc.com
Subject: Re: [PATCH v4] sh: Restructure setup code to reserve memory regions earlier
Date: Tue, 23 Jul 2024 09:57:05 +0200	[thread overview]
Message-ID: <d12de025cfb71bcf2a86aa54251aac20f16d32b7.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <636943c1-6e32-4dd1-abdd-5a110e9aa07c@quicinc.com>

Hi Oreluwa,

On Wed, 2024-07-17 at 19:22 -0700, Oreoluwa Babatunde wrote:
> Thanks for your feedback and for working with me on this.
> I have uploaded a new version here:
> https://lore.kernel.org/all/20240718021822.1545976-1-quic_obabatun@quicinc.com/
> 
> Please let me know if this properly addresses your comments.

Thanks. I'll have another look this week, including testing.

But I have decided to send the pull request to Linus for v6.11 now,
so I don't have to hurry with the review.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  reply	other threads:[~2024-07-23  7:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11 21:44 [PATCH v4] sh: Restructure setup code to reserve memory regions earlier Oreoluwa Babatunde
2024-07-12 13:12 ` John Paul Adrian Glaubitz
2024-07-13  7:58 ` John Paul Adrian Glaubitz
2024-07-16  0:12   ` Oreoluwa Babatunde
2024-07-16 10:42     ` John Paul Adrian Glaubitz
2024-07-18  2:22       ` Oreoluwa Babatunde
2024-07-23  7:57         ` John Paul Adrian Glaubitz [this message]
2024-07-23 16:59           ` Oreoluwa Babatunde
2024-08-17  7:14             ` John Paul Adrian Glaubitz

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=d12de025cfb71bcf2a86aa54251aac20f16d32b7.camel@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=dalias@libc.org \
    --cc=kernel@quicinc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=quic_obabatun@quicinc.com \
    --cc=robh+dt@kernel.org \
    --cc=ysato@users.sourceforge.jp \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).