public inbox for linux-alpha@vger.kernel.org
 help / color / mirror / Atom feed
From: Askar Safin <safinaskar@gmail.com>
To: macro@orcam.me.uk
Cc: kernel-janitors@vger.kernel.org, linmag7@gmail.com,
	linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org,
	mattst88@gmail.com, patches@lists.linux.dev,
	richard.henderson@linaro.org
Subject: Re: [PATCH 1/1] alpha: trivial: remove ^L chars
Date: Sun, 11 Jan 2026 14:35:05 +0300	[thread overview]
Message-ID: <20260111113505.2146705-1-safinaskar@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2601061310110.45251@angie.orcam.me.uk>

"Maciej W. Rozycki" <macro@orcam.me.uk>:
>  As a matter of interest, why would the presence of ^L characters cause 
> any issues?  That is just another instance of white space and it has been 

I have shell script, which allows me to remove given config (for example,
CONFIG_NET) from whole Linux source tree. To do this, this script parses
.c files, Kconfig files and makefiles. So, I want them to be as predictable
and easy-to-parse as possible.

P. S. I don't see your emails in my gmail inbox (not even in spam folder).

-- 
Askar Safin

  parent reply	other threads:[~2026-01-11 11:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-28  6:34 [PATCH 0/1] alpha: trivial: remove ^L chars Askar Safin
2025-12-28  6:34 ` [PATCH 1/1] " Askar Safin
2026-01-05 10:38   ` Magnus Lindholm
2026-01-06 13:17     ` Maciej W. Rozycki
2026-01-06 16:30       ` Magnus Lindholm
2026-01-06 17:17         ` Maciej W. Rozycki
2026-01-11 11:35       ` Askar Safin [this message]
2026-01-11 17:58         ` Maciej W. Rozycki

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=20260111113505.2146705-1-safinaskar@gmail.com \
    --to=safinaskar@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linmag7@gmail.com \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=mattst88@gmail.com \
    --cc=patches@lists.linux.dev \
    --cc=richard.henderson@linaro.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