All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Daniele Nicolodi <daniele@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] [git pull] Patch queue for 2.5.x
Date: Sat, 02 Oct 2010 11:15:53 +0200	[thread overview]
Message-ID: <4CA6F849.3060301@domain.hid> (raw)
In-Reply-To: <4CA6F124.3090006@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]

Am 02.10.2010 10:45, Daniele Nicolodi wrote:
> On 02/10/10 08:40, Jan Kiszka wrote:
>> The following changes since commit 5e7cfa5c25672e4478a721eadbd6f6c5b4f88a2f:
>>
>>   nucleus/sched: fix rescheduling bit test macros (2010-09-30 02:34:27 +0200)
>>
>> are available in the git repository at:
>>   git://git.xenomai.org/xenomai-jki.git for-2.5.x
>>
>> Jan Kiszka (8):
>>       RTDM: Protect xnshadow_ppd_get via nklock
>>       Fix symbolic status ouput of root threads
>>       Create watchdog as non-blockable timer
>>       native: Improve documentation of rt_task_join and rt_task_delete
>>       x86: Add PCI ID of Series 5/3400 Intel chipset to SMI workaround
>>       x86: Add PCI ID of 631xESB/632xESB/3100 Intel chipset to SMI workaround
>>       x86: Add PCI ID of Intel ICH9M-E chipset to SMI workaround
> 
> This patch reads:
> 
> +#ifdef PCI_DEVICE_ID_INTEL_ICH9_1
> +#define PCI_DEVICE_ID_INTEL_ICH9_1 0x2917
> +#endif
> 
> shouldn't it be #ifndef ... #define ... #endif instead?
> 
>>       x86: Add PCI ID of Intel ICH9M chipset to SMI workaround
> 
> Same for this one.

Indeed. Fixed in both branches, and I also cleaned up a typo in some
patch description. Updates pushed.

Thanks,
Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

  reply	other threads:[~2010-10-02  9:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-02  6:40 [Xenomai-core] [git pull] Patch queue for 2.5.x Jan Kiszka
2010-10-02  8:45 ` Daniele Nicolodi
2010-10-02  9:15   ` Jan Kiszka [this message]
2010-10-02 23:35     ` Gilles Chanteperdrix
2010-10-04  9:28       ` Jan Kiszka

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=4CA6F849.3060301@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=daniele@domain.hid \
    --cc=xenomai@xenomai.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.