public inbox for linux-kernel-mentees@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: Lasse Collin <lasse.collin@tukaani.org>
To: Kuan-Wei Chiu <visitorckw@gmail.com>,
	Ankan Biswas <spyjetfayed@gmail.com>
Cc: skhan@linuxfoundation.org, khalid@kernel.org,
	david.hunter.linux@gmail.com, linux-kernel@vger.kernel.org,
	linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH v2] lib/xz: remove dead IA-64 (Itanium) support code
Date: Mon, 13 Oct 2025 23:44:07 +0300	[thread overview]
Message-ID: <20251013234407.11e70f22.lasse.collin@tukaani.org> (raw)
In-Reply-To: <aO1gOckA14Ed/26F@visitorckw-System-Product-Name>

On 2025-10-14 Kuan-Wei Chiu wrote:
> On Mon, Oct 13, 2025 at 11:01:58PM +0530, Ankan Biswas wrote:
> > Note that the upstream version of xz_dec_bcj.c still retains support
> > for the IA-64 BCJ filter.  
> 
> Not sure if it's necessary to mention this, but I guess it's fine.

Information about upstream version isn't needed in Linux commit log, so
that sentence could be omitted.

> I'm not quite sure what you changed in v2 compared to v1.

It added the second hunk to the diff of xz_private.h.

> Lasse,
> Since this change is located under lib/, I assume it will be routed
> through Andrew's tree?
> If that's the case, then perhaps we should also Cc Andrew.

Yes, putting him into the To field and others as Cc should make the
patch go forward. Sorry that I didn't notice and comment this myself
earlier.

-- 
Lasse Collin

  reply	other threads:[~2025-10-13 20:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-13 17:31 [PATCH v2] lib/xz: remove dead IA-64 (Itanium) support code Ankan Biswas
2025-10-13 20:25 ` Kuan-Wei Chiu
2025-10-13 20:44   ` Lasse Collin [this message]
2025-10-14  4:55     ` Ankan Biswas

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=20251013234407.11e70f22.lasse.collin@tukaani.org \
    --to=lasse.collin@tukaani.org \
    --cc=david.hunter.linux@gmail.com \
    --cc=khalid@kernel.org \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=spyjetfayed@gmail.com \
    --cc=visitorckw@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