All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>,
	yung-chuan.liao@linux.intel.com,
	pierre-louis.bossart@linux.intel.com,
	krzysztof.kozlowski@linaro.org, alsa-devel@alsa-project.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH stable-6.10 regression] Revert "soundwire: stream: fix programming slave ports for non-continous port maps"
Date: Mon, 16 Sep 2024 09:49:03 +0200	[thread overview]
Message-ID: <Zufi79wdsMokxVB9@vaman> (raw)
In-Reply-To: <2024091555-untitled-bunkbed-8151@gregkh>

On 15-09-24, 15:23, Greg KH wrote:
> On Sun, Sep 15, 2024 at 12:45:25AM +0530, Vinod Koul wrote:
> > > > 
> > > > Is this in Linus's tree yet?  That's what we are waiting for.
> > > 
> > > Yes I was waiting for that as well, the pull request has been sent to
> > > Linus, this should be in his tree, hopefully tomorow..
> > 
> > It is in Linus's tree now. Greg would you like to drop commit
> > 6fa78e9c41471fe43052cd6feba6eae1b0277ae3 or carry it and the
> > revert...?
> 
> I can not "drop" a commit that is already in a realease for obvious
> reasons :(
> 
> > What is the usual process for you to handle reverts?
> 
> We just take them like normal.  What is the git id of the revert in
> Linus's tree?

Sure, makes sense. It has been auto-picked so this is fine.

fwiw: 
ab8d66d132bc: soundwire: stream: fix programming slave ports for non-continous port maps

Thanks
-- 
~Vinod

      reply	other threads:[~2024-09-16  7:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-10 12:40 [PATCH stable-6.10 regression] Revert "soundwire: stream: fix programming slave ports for non-continous port maps" Peter Ujfalusi
2024-09-10 13:02 ` Péter Ujfalusi
2024-09-11 12:31   ` Greg KH
2024-09-11 14:31     ` Linux regression tracking (Thorsten Leemhuis)
2024-09-16  7:50       ` Vinod Koul
2024-09-13 11:51     ` Vinod Koul
2024-09-14 19:15       ` Vinod Koul
2024-09-15 13:23         ` Greg KH
2024-09-16  7:49           ` Vinod Koul [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=Zufi79wdsMokxVB9@vaman \
    --to=vkoul@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=stable@vger.kernel.org \
    --cc=yung-chuan.liao@linux.intel.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 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.