linux-alpha.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Turner <mattst88@gmail.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Richard Henderson <rth@twiddle.net>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	linux-alpha <linux-alpha@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Alpha: Remove redundant local asm header redirections
Date: Thu, 14 Apr 2022 16:06:17 -0700	[thread overview]
Message-ID: <CAEdQ38EpBMnkP-PNZnwaoO4poFJQO5YSFJeZgiQ-obJmjogBFQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2202131944000.34636@angie.orcam.me.uk>

On Sun, Feb 13, 2022 at 12:01 PM Maciej W. Rozycki <macro@orcam.me.uk> wrote:
>
> Remove a number of asm headers locally redirected to the respective
> generic or generated versions.
>
> For asm-offsets.h all that is needed is a Kbuild entry for the generic
> version, and for div64.h, irq_regs.h and kdebug.h nothing is needed as
> in their absence they will be redirected automatically according to
> include/asm-generic/Kbuild.
>
> Signed-off-by: Maciej W. Rozycki <macro@orcam.me.uk>
> ---
> Hi,
>
>  Noticed while fiddling with Kbuild for PARPORT_PC.  Please apply.
>
>   Maciej


Sorry for the delay. I'll apply this. I just haven't had much time for
alphas lately.

Maybe now's a good time to remind you that I'm still waiting on you to
upstream the m41t80/SWARM/i2c/smbus patches? It's been more than 11
years now, so it seems long enough for a ping :)

  parent reply	other threads:[~2022-04-14 23:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-13 20:01 [PATCH] Alpha: Remove redundant local asm header redirections Maciej W. Rozycki
2022-03-01 20:52 ` [PING][PATCH] " Maciej W. Rozycki
2022-03-31 15:22 ` [PING^2][PATCH] " Maciej W. Rozycki
2022-04-13 22:53 ` [PING^3][PATCH] " Maciej W. Rozycki
2022-04-14  7:30   ` John Paul Adrian Glaubitz
2022-04-14 23:06 ` Matt Turner [this message]
2022-04-15 12:26   ` [PATCH] " Maciej W. Rozycki
2023-02-26  2:08     ` Matt Turner
2023-02-27 16:27       ` 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=CAEdQ38EpBMnkP-PNZnwaoO4poFJQO5YSFJeZgiQ-obJmjogBFQ@mail.gmail.com \
    --to=mattst88@gmail.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=rth@twiddle.net \
    /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).