From: 'Greg KH' <gregkh@linuxfoundation.org>
To: Soha Jin <soha@lohu.info>
Cc: rafael@kernel.org, linux-kernel@vger.kernel.org,
'Wende Tan' <twd2.me@gmail.com>
Subject: Re: PING: [PATCH] platform: use fwnode_irq_get_byname instead of of_irq_get_byname to get irq
Date: Thu, 10 Nov 2022 18:55:49 +0100 [thread overview]
Message-ID: <Y207JTskpwEUTD7X@kroah.com> (raw)
In-Reply-To: <07EF40D2C259BC45+249601d8dc76$f05f03c0$d11d0b40$@lohu.info>
On Mon, Oct 10, 2022 at 03:07:19PM +0800, Soha Jin wrote:
> > -----Original Message-----
> > From: Greg KH <gregkh@linuxfoundation.org>
> > Sent: Monday, October 10, 2022 2:22 PM
> >
> > It's the middle of the merge window, we can't do anything until after
> > 6.1-rc1 is out, please relax and wait for that.
> >
> > And what is the rush here, what is broken without this change?
> >
>
> Got it, just wondering if there anything I could improve in this patch,
> since I have not got any feedback. The bug just affect named interrupts in
> ACPI, which seems not used widely and not in a hurry.
Your patch is corrupted and can not be applied :(
You could have tested this by picking it up from lore.kernel.org and
verified that it worked.
Please fix your email client and send a new version.
thanks,
greg k-h
next prev parent reply other threads:[~2022-11-10 17:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 18:15 [PATCH] platform: use fwnode_irq_get_byname instead of of_irq_get_byname to get irq soha
2022-10-10 3:14 ` PING: " Soha Jin
2022-10-10 6:21 ` Greg KH
2022-10-10 7:07 ` Soha Jin
2022-11-10 17:55 ` 'Greg KH' [this message]
2022-11-10 18:01 ` Soha Jin
2022-11-10 17:55 ` Greg KH
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=Y207JTskpwEUTD7X@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=soha@lohu.info \
--cc=twd2.me@gmail.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