From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-arch@vger.kernel.org, linux-parisc@vger.kernel.org,
Vineet Gupta <vgupta@kernel.org>
Subject: Re: [RFC][PATCHES] asm/unaligned.h removal
Date: Wed, 2 Oct 2024 23:17:49 +0100 [thread overview]
Message-ID: <20241002221749.GI4017910@ZenIV> (raw)
In-Reply-To: <CAHk-=wj7f32w8p1OrN4fahaF+44zWfTAD+3ucd=XETM_Pt-=6A@mail.gmail.com>
On Wed, Oct 02, 2024 at 11:33:23AM -0700, Linus Torvalds wrote:
> On Tue, 1 Oct 2024 at 12:51, Al Viro <viro@zeniv.linux.org.uk> wrote:
> >
> > Please, review. I don't really care which tree(s) does that stuff
> > go through; I can put the first two in my #for-next, as long as nobody
> > has objections to the patches themselves.
>
> Please just add the whole series to your tree. I see you already got
> the ack for the parisc side, the arc side looks fine too.
Both parisc and arc are already in my tree; do you really want the
autogenerated patch to be there as well? Would be a recurring headache
through the cycle - anyone adding an include of that sucker in their
branch would have to do an explicit merge from that branch first, or
deal with the silent conflicts on merge to -next (well, silent as in
"git doesn't warn you"; build breakage will be there).
I suppose I could do that autogenerated commit + replacement of
asm-generic/unaligned.h with #include <linux/unaligned.h>,
then take the newly added includes of <asm{,-generic}/unaligned.h> after -rc1,
with asm-generic/unaligned.h taken out once all strays are gone, but that
feels too convoluted...
Or am I misparsing you?
> And even if there is some further fixup required, I'd rather just have
> this done and do any possible fixups later than have some kind of
> "wait for everybody to ack it".
next prev parent reply other threads:[~2024-10-02 22:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 19:51 [RFC][PATCHES] asm/unaligned.h removal Al Viro
2024-10-01 19:51 ` [PATCH 1/3] parisc: get rid of private asm/unaligned.h Al Viro
2024-10-02 0:57 ` Helge Deller
2024-10-02 3:23 ` Al Viro
2024-10-02 8:10 ` Rolf Eike Beer
2024-10-01 19:53 ` [PATCH 2/3] arc: " Al Viro
2024-10-02 21:03 ` Vineet Gupta
2024-10-02 21:24 ` Al Viro
2024-10-01 19:54 ` [PATCH 3/3] move asm/unaligned.h to linux/unaligned.h Al Viro
2024-10-01 20:34 ` [RFC][PATCHES] asm/unaligned.h removal Al Viro
2024-10-02 18:33 ` Linus Torvalds
2024-10-02 22:17 ` Al Viro [this message]
2024-10-02 23:36 ` [git pull] " Al Viro
2024-10-03 0:04 ` pr-tracker-bot
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=20241002221749.GI4017910@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-arch@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vgupta@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.