From: "Jan Beulich" <JBeulich@suse.com>
To: "Bjorn Helgaas" <bhelgaas@google.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-pci@vger.kernel.org>,
"Jesse Barnes" <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH 1/5, resend] PCI: adjust quirk handler section annotations
Date: Wed, 09 May 2012 17:56:26 +0100 [thread overview]
Message-ID: <4FAABDDA0200007800082998@nat28.tlf.novell.com> (raw)
In-Reply-To: <CAErSpo5Aidio0a6SjeYu=-9gXJU1aALMi5mUjg2aEB5pTsr8=Q@mail.gmail.com>
>>> On 09.05.12 at 18:08, Bjorn Helgaas <bhelgaas@google.com> wrote:
> On Wed, May 9, 2012 at 9:02 AM, Jan Beulich <JBeulich@suse.com> wrote:
>>>>> On 09.05.12 at 17:54, Bjorn Helgaas <bhelgaas@google.com> wrote:
>>> My inclination is that all PCI fixups should work the same for
>>> hot-added devices as for those present at boot, which would suggest
>>> that we should always use __devinit, not __init. If I'm missing
>>> something, please educate me :)
>>
>> That's certainly possible - I simply based the patch on what is there
>> currently.
>
> Yep, your patch makes perfect sense considering the tree as it is
> today. But if you agree with my sense of what it *should* be, I think
> we should leave things as they are, or work on moving everything
I indeed wondered why it isn't that way while doing this.
> towards __devinit (I'd be thrilled if you wanted to work on that :)).
> Otherwise we'd just be changing things to __init that we'd have to
> change back later.
I'd perhaps rather drop my patches then, as the main benefit
(moving stuff from resident text to init text) would go away.
Jan
prev parent reply other threads:[~2012-05-09 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 8:43 Jan Beulich
2012-05-09 15:54 ` Bjorn Helgaas
2012-05-09 16:02 ` Jan Beulich
2012-05-09 16:08 ` Bjorn Helgaas
2012-05-09 16:56 ` Jan Beulich [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=4FAABDDA0200007800082998@nat28.tlf.novell.com \
--to=jbeulich@suse.com \
--cc=bhelgaas@google.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®