From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Lee Jones <lee@kernel.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "mfd: syscon: Remove repetition of the regmap_get_val_endian()"
Date: Mon, 10 Oct 2022 09:25:22 -0600 [thread overview]
Message-ID: <Y0Q5Yn8w91KePV5a@zx2c4.com> (raw)
In-Reply-To: <Y0POMogrdDN+BR37@google.com>
On Mon, Oct 10, 2022 at 08:48:02AM +0100, Lee Jones wrote:
> On Sat, 08 Oct 2022, Andy Shevchenko wrote:
> > > And if not, please just send me the revert through the normal channels. Ok?
> >
> > Yeah, revert is a good move here.
>
> Thanks for the clarification Andy.
>
> Linus, by normal channels, do you mean you'd like a follow-up PR?
I would assume so.
What happened here is that I sent you (Lee) and Andy this patch, but
also had Linus in the recipient list because I sent this as a reply to
my initial message on the pull request thread, creating some ambiguity.
Sometimes when Linus is on the CC like that, it's an indication that
he's to take it directly. That's not the plan here. Rather, I think the
idea is that you can queue it up in your tree, and send it out with the
next PR of fixes for 6.1.
Jason
next prev parent reply other threads:[~2022-10-10 15:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 9:02 [GIT PULL] MFD for v6.1 Lee Jones
2022-10-07 19:20 ` pr-tracker-bot
2022-10-08 15:39 ` Jason A. Donenfeld
2022-10-08 15:47 ` [PATCH] Revert "mfd: syscon: Remove repetition of the regmap_get_val_endian()" Jason A. Donenfeld
2022-10-08 16:45 ` Linus Torvalds
2022-10-08 19:07 ` Andy Shevchenko
2022-10-10 7:48 ` Lee Jones
2022-10-10 15:25 ` Jason A. Donenfeld [this message]
2022-10-11 7:39 ` Lee Jones
2022-10-11 9:44 ` Andy Shevchenko
2022-10-11 9:44 ` Andy Shevchenko
2022-10-18 7:23 ` Lee Jones
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=Y0Q5Yn8w91KePV5a@zx2c4.com \
--to=jason@zx2c4.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=lee@kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox