From: "Liuweni" <qingshenlwy@gmail.com>
To: "Jiri Kosina" <jkosina@suse.cz>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Re: [PATCH]kernel/irq/chip.c:Modify the code note
Date: Wed, 4 Nov 2009 22:31:27 +0800 [thread overview]
Message-ID: <200911042231252503000@gmail.com> (raw)
In-Reply-To: 200911042011027500109@gmail.com
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb2312", Size: 1850 bytes --]
Thank you very much.
Someone tell me that my pre-mail's format is incorrect. The correct format is
......
Changlog
......
Signed-off-by: yourname <your@mail>
----------------------
patch context
And I have not received your mail. Maybe The gmail play a trick.
Then, I re-submitt this hunk after a week.
But now, I have found your mail in the mail-list.
2009-11-04
Liuweni
·¢¼þÈË£º Jiri Kosina
·¢ËÍʱ¼ä£º 2009-11-04 21:06:24
ÊÕ¼þÈË£º Liuweni
³ËÍ£º linux-kernel; qingshenlwy; xgr178
Ö÷Ì⣺ Re: [PATCH]kernel/irq/chip.c:Modify the code note
On Wed, 4 Nov 2009, Liuweni wrote:
> In the origin, the code notes are not fit for set_irq_msi.
> The function name is set_irq_data.
>
> And, I change function note "handle_percpu_IRQ" to "handle_percpu_irq".
>
>
> Signed-off-by: Liuwenyi <qingshenlwy@gmail.com>
>
> ------------------------------------------
> diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c
> index c166019..ba566c2 100644
> --- a/kernel/irq/chip.c
> +++ b/kernel/irq/chip.c
> @@ -166,11 +166,11 @@ int set_irq_data(unsigned int irq, void *data)
> EXPORT_SYMBOL(set_irq_data);
>
> /**
> - * set_irq_data - set irq type data for an irq
> + * set_irq_msi - set MSI descriptor data for an irq
> * @irq: Interrupt number
> * @entry: Pointer to MSI descriptor data
> *
> - * Set the hardware irq controller data for an irq
> + * Set the MSI descriptor entry for an irq
> */
You have submitted this hunk separately before, and I already have it in
my queue (and I have sent you a mail informing you about this being
merged), so you'd better not include it as part of any further patch
submissions.
--
Jiri Kosina
SUSE Labs, Novell Inc.
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
prev parent reply other threads:[~2009-11-04 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 12:11 [PATCH]kernel/irq/chip.c:Modify the code note Liuweni
2009-11-04 13:06 ` Jiri Kosina
2009-11-04 14:31 ` Liuweni [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=200911042231252503000@gmail.com \
--to=qingshenlwy@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@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.