qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Paul Brook <paul@codesourcery.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Register uhci_reset() callback.
Date: Mon, 15 Jun 2009 20:21:32 +0300	[thread overview]
Message-ID: <20090615172132.GB3964@redhat.com> (raw)
In-Reply-To: <4A368214.6060508@redhat.com>

On Mon, Jun 15, 2009 at 08:17:08PM +0300, Avi Kivity wrote:
> On 06/15/2009 08:02 PM, Gleb Natapov wrote:
>> On Mon, Jun 15, 2009 at 07:21:09PM +0300, Avi Kivity wrote:
>>    
>>> On 06/11/2009 04:46 PM, Gleb Natapov wrote:
>>>      
>>>> On Thu, Jun 11, 2009 at 02:41:33PM +0100, Paul Brook wrote:
>>>>
>>>>        
>>>>> On Thursday 11 June 2009, Gleb Natapov wrote:
>>>>>
>>>>>          
>>>>>> Update IRQ line on reset.
>>>>>>
>>>>>>            
>>>>> This should not be necessary.
>>>>>
>>>>>
>>>>>          
>>>> You are always so brief.
>>>>        
>>> To be fair, so are you.
>>>
>>>      
>> May be, but in this case after previous patch to reset interrupt level
>> for each device at PCI bridge level was rejected on the premise that
>> device should lower its own irq line on reset and since patches started
>> flowing in to do just that, I did not expect that eloquent explanation
>> would be needed for such trivial and obviously correct change.
>>    
>
> Citing which guests are unbroken by the patch, for example, would have  
> helped.  As someone who accepts a lot of excellent patches from you, I  
> also find the change logs to be laconic.
>
I agree, I will resend the patch with more detailed changelog. But reset
handler should be added to each device (and PCI devices reset should
lower interrupt line since it may be shared) even if there is no
reproducible test case to show.

I'll try to work on improving my commit logs :)

--
			Gleb.

  reply	other threads:[~2009-06-15 17:23 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11  8:48 [Qemu-devel] Register uhci_reset() callback Gleb Natapov
2009-06-11 13:41 ` Paul Brook
2009-06-11 13:46   ` Gleb Natapov
2009-06-11 13:53     ` Paul Brook
2009-06-11 14:00       ` Gleb Natapov
2009-06-11 16:38         ` Jamie Lokier
2009-06-11 16:40           ` Gleb Natapov
2009-06-15 16:20             ` Avi Kivity
2009-06-16 15:00               ` Jamie Lokier
2009-06-16 15:18                 ` Avi Kivity
2009-06-16 15:43                   ` Jamie Lokier
2009-06-15 16:21     ` Avi Kivity
2009-06-15 17:02       ` Gleb Natapov
2009-06-15 17:17         ` Avi Kivity
2009-06-15 17:21           ` Gleb Natapov [this message]
2009-06-15 17:56         ` Paul Brook
2009-06-15 18:16           ` Gleb Natapov
2009-06-15 18:57             ` Blue Swirl
2009-06-15 19:30               ` Gleb Natapov
2009-06-15 19:50                 ` Blue Swirl
2009-06-15 20:05                   ` Gleb Natapov
2009-06-16 15:14                     ` Blue Swirl
2009-06-16 15:20                       ` Gleb Natapov
2009-06-16 16:54                         ` Blue Swirl
2009-06-16 17:09                           ` Gleb Natapov
2009-06-16 17:19                             ` Blue Swirl
2009-06-16 18:39                               ` Gleb Natapov
2009-06-18  9:20                               ` Avi Kivity
2009-06-16 16:54                         ` Paul Brook
2009-06-16 17:12                           ` Blue Swirl
2009-06-16 18:00                             ` Paul Brook
2009-06-16 18:10                               ` Blue Swirl
2009-06-16 18:52                                 ` Jamie Lokier
2009-06-16 19:05                                   ` Jamie Lokier
2009-06-16 19:10                                     ` Blue Swirl
2009-06-16 19:23                                       ` Gleb Natapov
2009-06-16 19:16                                   ` Paul Brook
2009-06-16 17:47                           ` Gleb Natapov
2009-06-16 17:04                 ` Paul Brook

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=20090615172132.GB3964@redhat.com \
    --to=gleb@redhat.com \
    --cc=avi@redhat.com \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).