All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Breathitt Gray <wbg@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: William Breathitt Gray <wbg@kernel.org>, linux-iio@vger.kernel.org
Subject: Re: [PULL] Counter fixes for 6.15
Date: Thu, 22 May 2025 19:13:22 +0900	[thread overview]
Message-ID: <20250522101325.779686-1-wbg@kernel.org> (raw)
In-Reply-To: <2025052145-culprit-underdone-c69b@gregkh>

On Wed, May 21, 2025 at 02:07:29PM +0200, Greg KH wrote:
> On Sun, May 11, 2025 at 03:43:29PM +0900, William Breathitt Gray wrote:
> > The following changes since commit b4432656b36e5cc1d50a1f2dc15357543add530e:
> >
> >   Linux 6.15-rc4 (2025-04-27 15:19:23 -0700)
> >
> > are available in the Git repository at:
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/wbg/counter.git tags/counter-fixes-for-6.15
> >
> > for you to fetch changes up to 7351312632e831e51383f48957d47712fae791ef:
> >
> >   counter: interrupt-cnt: Protect enable/disable OPs with mutex (2025-05-03 08:45:11 +0900)
> >
> > ----------------------------------------------------------------
> > Counter fixes for 6.15
> >
> > A fix to prevent a race condition when accessing the Count enable
> > component in interrupt-cnt.
> 
> I took this into my -next branch BUT for some reason you have this
> commit with a Fixes: tag but NO Cc: stable tag.  Which means it will not
> get pulled into the stable trees automatically.  Are you sure you wanted
> to do that?

Sorry, the missing Cc: stable tag was an oversight; this fix should be
pulled into the stable trees as well. What would be the best way for me
to resolve this, should I RESEND the patch with the appropriate tag and
Cc stable@vger.kernel.org?

Thanks,

William Breathitt Gray

  reply	other threads:[~2025-05-22 10:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-11  6:43 [PULL] Counter fixes for 6.15 William Breathitt Gray
2025-05-21 12:07 ` Greg KH
2025-05-22 10:13   ` William Breathitt Gray [this message]
2025-05-22 11:12     ` Greg KH
2025-05-22 11:17       ` William Breathitt Gray

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=20250522101325.779686-1-wbg@kernel.org \
    --to=wbg@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-iio@vger.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.