From: Greg KH <gregkh@linuxfoundation.org>
To: Sasha Finkelstein <fnkl.kernel@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
linux-bluetooth@vger.kernel.org, stable@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] bluetooth: btbcm: Fix logic error in forming the board name.
Date: Fri, 10 Mar 2023 10:53:17 +0100 [thread overview]
Message-ID: <ZAr+DWZ9bt3ZxpCs@kroah.com> (raw)
In-Reply-To: <CAMT+MTT1RE2M0Fn3k+EXO=WNgAvNGPGHpidpTp0Jdus61M5UPw@mail.gmail.com>
On Fri, Mar 10, 2023 at 10:41:28AM +0100, Sasha Finkelstein wrote:
> > <formletter>
> >
> > This is not the correct way to submit patches for inclusion in the
> > stable kernel tree. Please read:
> > https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> > for how to do this properly.
> >
> > </formletter>
> Sorry about that, let's just skip the stable tree part for now then.
That's not how to solve the problem, if it's a bug that needs to be
fixed in stable kernels, submit it properly and it will automatically be
propagated there as the documentation states.
thanks,
greg k-h
next prev parent reply other threads:[~2023-03-10 9:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 8:07 [PATCH RESEND] bluetooth: btbcm: Fix logic error in forming the board name Sasha Finkelstein
2023-03-10 8:07 ` Sasha Finkelstein via B4 Relay
2023-03-10 8:09 ` kernel test robot
2023-03-10 8:10 ` Greg KH
2023-03-10 9:41 ` Sasha Finkelstein
2023-03-10 9:53 ` Greg KH [this message]
2023-03-10 8:40 ` [RESEND] " bluez.test.bot
-- strict thread matches above, loose matches on Subject: below --
2023-03-10 10:28 [PATCH RESEND] " Sasha Finkelstein
2023-03-10 10:28 ` Sasha Finkelstein via B4 Relay
2023-03-14 23:10 ` patchwork-bot+bluetooth
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=ZAr+DWZ9bt3ZxpCs@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=fnkl.kernel@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=stable@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.