From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Takashi Iwai <tiwai@suse.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the ieee1394 tree
Date: Fri, 2 Aug 2024 21:15:43 +0900 [thread overview]
Message-ID: <20240802121543.GA113551@workstation.local> (raw)
In-Reply-To: <87mslvig7e.wl-tiwai@suse.de>
Hi,
On Fri, Aug 02, 2024 at 08:36:37AM +0200, Takashi Iwai wrote:
> On Fri, 02 Aug 2024 04:21:20 +0200,
> Stephen Rothwell wrote:
> >
> > Hi all,
> >
> > The following commits are also in the sound-current tree as different
> > commits (but the same patches):
> >
> > c2f9fd3d6ad7 ("Revert "ALSA: firewire-lib: operate for period elapse event in process context"")
> > e29ed9a81fd4 ("Revert "ALSA: firewire-lib: obsolete workqueue for period update"")
>
> Sakamoto-san, with your Reviewed-by tag, I thought you gave a sign to
> put via sound git tree? I'm going send a PR to Linus in today, so if
> possible, please drop those from yours.
Oops. When applying the recent patch[1] to the for-next branch, I
wrongly pushed these patches under my evaluation to the remote. They
should be sent by sound side, indeed.
I pushed the revised series to the for-next branch. Thanks for noticing
it, guys.
[1] https://lore.kernel.org/lkml/20240801022629.31857-1-o-takashi@sakamocchi.jp/
Regards
Takashi Sakamoto
prev parent reply other threads:[~2024-08-02 12:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 2:21 linux-next: duplicate patches in the ieee1394 tree Stephen Rothwell
2024-08-02 6:36 ` Takashi Iwai
2024-08-02 12:15 ` Takashi Sakamoto [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=20240802121543.GA113551@workstation.local \
--to=o-takashi@sakamocchi.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tiwai@suse.de \
/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