From: Greg KH <gregkh@linuxfoundation.org>
To: Asmaa Mnebhi <asmaa@nvidia.com>
Cc: "kernel-team@lists.ubuntu.com" <kernel-team@lists.ubuntu.com>,
Khoa Vo <khoav@nvidia.com>, Meriton Tuli <meriton@nvidia.com>,
Vladimir Sokolovsky <vlad@nvidia.com>,
Shreeya Patel <shreeya.patel@collabora.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [SRU][F:linux-bluefield][PATCH v2 1/2] gpio: Restrict usage of GPIO chip irq members before initialization
Date: Fri, 17 Feb 2023 16:43:51 +0100 [thread overview]
Message-ID: <Y++gtz7DQc4x5UG6@kroah.com> (raw)
In-Reply-To: <CH2PR12MB3895AFD55DBF315028F72CF0D7A19@CH2PR12MB3895.namprd12.prod.outlook.com>
On Fri, Feb 17, 2023 at 03:33:28PM +0000, Asmaa Mnebhi wrote:
> Hi Greg,
>
> Apologies, This is not meant for the Linux kernel. You got spammed because when I cherry-picked this change for canonical only (kernel-team@lists.ubuntu.com), this got added to the patches:
> > Signed-off-by: Shreeya Patel <shreeya.patel@collabora.com>
> > Cc: stable@vger.kernel.org
> > Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> > Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> > Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl> (backported from
> > commit 5467801f1fcbdc46bc7298a84dbf3ca1ff2a7320)
> > Signed-off-by: Asmaa Mnebhi <asmaa@nvidia.com>
>
> Which caused it to be sent to everyone.
> Will talk to canonical on how to avoid this in the future.
If Canonical just took the normal upstream stable releases (which this
commit is already included in), this wouldn't be an issue at all. Why
do they not do that?
thanks,
greg k-h
next prev parent reply other threads:[~2023-02-17 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230217140744.20600-1-asmaa@nvidia.com>
2023-02-17 14:07 ` [SRU][F:linux-bluefield][PATCH v2 1/2] gpio: Restrict usage of GPIO chip irq members before initialization Asmaa Mnebhi
2023-02-17 14:26 ` Greg KH
2023-02-17 15:33 ` Asmaa Mnebhi
2023-02-17 15:43 ` Greg KH [this message]
2023-02-17 14:07 ` [SRU][F:linux-bluefield][PATCH v2 2/2] gpio: Request interrupts after IRQ is initialized Asmaa Mnebhi
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=Y++gtz7DQc4x5UG6@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=asmaa@nvidia.com \
--cc=brgl@bgdev.pl \
--cc=kernel-team@lists.ubuntu.com \
--cc=khoav@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=meriton@nvidia.com \
--cc=shreeya.patel@collabora.com \
--cc=stable@vger.kernel.org \
--cc=vlad@nvidia.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