From: Isaac Scott <isaac.scott@ideasonboard.com>
To: Mark Brown <broonie@kernel.org>
Cc: michael.hennerich@analog.com, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org, dheeraj.linuxdev@gmail.com
Subject: Re: [PATCH 1/1] regulator: ad5398: Correct the SW_POWER_DOWN bit number
Date: Thu, 06 Feb 2025 13:57:14 +0000 [thread overview]
Message-ID: <1da6b6e3f9cd1abd84cc5d3d73a2ad3d1340914d.camel@ideasonboard.com> (raw)
In-Reply-To: <28767ef9-0909-4d74-99fa-514c9bc99afc@sirena.org.uk>
On Thu, 2025-02-06 at 13:44 +0000, Mark Brown wrote:
> On Thu, Feb 06, 2025 at 01:28:15PM +0000, Isaac Scott wrote:
> > On Thu, 2025-02-06 at 12:58 +0000, Mark Brown wrote:
>
> > > You didn't include a Fixes tag or otherwise mention that this was
> > > a
> > > fix
> > > for a recent change so I was applying this as a fix for Linus'
> > > tree.
>
> > To be clear, would you like me to resend the patch with the fixes
> > tag?
>
> Yes, like the message said please resend. Though isn't this the same
> as
> the fix that Dheeraj already sent:
>
Yes, we have both fixed the same thing! Although I wasn't CC'd so I
didn't know they fixed my patch.
Best wishes,
Isaac
>
> https://lore.kernel.org/r/20250206103153.59114-1-dheeraj.linuxdev@gmail.com
next prev parent reply other threads:[~2025-02-06 13:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 12:24 [PATCH 0/1] regulator: ad5398: Correct " Isaac Scott
2025-02-06 12:24 ` [PATCH 1/1] regulator: ad5398: Correct the " Isaac Scott
2025-02-06 12:28 ` Mark Brown
2025-02-06 12:45 ` Isaac Scott
2025-02-06 12:58 ` Mark Brown
2025-02-06 13:28 ` Isaac Scott
2025-02-06 13:44 ` Mark Brown
2025-02-06 13:57 ` Isaac Scott [this message]
2025-02-06 14:03 ` Mark Brown
2025-02-06 12:27 ` [PATCH 0/1] regulator: ad5398: Correct " Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2025-02-06 12:21 Isaac Scott
2025-02-06 12:21 ` [PATCH 1/1] regulator: ad5398: Correct the " Isaac Scott
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=1da6b6e3f9cd1abd84cc5d3d73a2ad3d1340914d.camel@ideasonboard.com \
--to=isaac.scott@ideasonboard.com \
--cc=broonie@kernel.org \
--cc=dheeraj.linuxdev@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.com \
/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
all inboxes | Powered by JetHome®