All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Brian Cain <bcain@quicinc.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"linux-hexagon@vger.kernel.org" <linux-hexagon@vger.kernel.org>,
	"patches@lists.linux.dev" <patches@lists.linux.dev>,
	"llvm@lists.linux.dev" <llvm@lists.linux.dev>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] hexagon: Disable constant extender optimization for LLVM prior to 19.1.0
Date: Wed, 18 Dec 2024 11:23:33 -0700	[thread overview]
Message-ID: <20241218182333.GB2948182@ax162> (raw)
In-Reply-To: <CH3SPRMB000129CE377EDA52BF102593B8052@CH3SPRMB0001.namprd02.prod.outlook.com>

Hi Brian,

On Wed, Dec 18, 2024 at 04:19:23AM +0000, Brian Cain wrote:
> > I'm sorry.  You should not have to send these changes to Linus. I should have
> > carried it in my tree and proposed it to Linus.
> > 
> > I'll do that, if you don't mind.
> 
> I see it's landed.  Sorry, all.  I'll resolve to do a better job here.

As Nick said, no worries, these things happen. If going straight to
Linus gave the impression that you did something wrong or inadequate, I
apologize, as that was not the intention. I seem to recall even recently
him saying that he does not mind applying patches directly from the
mailing list and bypassing the maintainer/subsystem when it fixes an
issue (cannot find the exact message I am thinking of but [1] is also
good). Since this patch is small and limited in scope, I figured it was
not worth any more pings.

That said, consistent ownership of arch/hexagon patches would not be a
bad thing going forward :)

[1]: https://lore.kernel.org/CAHk-=wgQhFPvneqAVXjUZDq=ahpATdgfg6LZ9n07MSSUGkQWuA@mail.gmail.com/

Cheers,
Nathan

      reply	other threads:[~2024-12-18 18:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-21 18:22 [PATCH v2] hexagon: Disable constant extender optimization for LLVM prior to 19.1.0 Nathan Chancellor
2024-12-17 17:44 ` Nathan Chancellor
2024-12-18  2:11   ` Brian Cain
2024-12-18  4:19     ` Brian Cain
2024-12-18 18:23       ` Nathan Chancellor [this message]

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=20241218182333.GB2948182@ax162 \
    --to=nathan@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bcain@quicinc.com \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=patches@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.