From: Rusty Russell <rusty@rustcorp.com.au>
To: mahatma@eu.by
Cc: linux-kernel@vger.kernel.org
Subject: Re: More modaliases + patchtool
Date: Thu, 19 Aug 2010 10:20:52 +0930 [thread overview]
Message-ID: <201008191020.52861.rusty@rustcorp.com.au> (raw)
In-Reply-To: <4C6BE292.3060307@bspu.unibel.by>
On Wed, 18 Aug 2010 11:09:30 pm Dzianis Kahanovich wrote:
> First I post into linux-modules@vger.kernel.org, but Jon Masters suggest to
> send this to you. There are some more against maillist:
>
> Some of modules have no MODULE_DEVICE_TABLE(...) and do not export hardware
> ("pnp") aliases, but have all required data to do this. I found it after
> ioatdma module (currently fixed in tree). This information may be useful to
> hardware/modules detection.
> [+] Also known problem: 2 modules (in 2.6.36 state) - scx200_acb.c & pch_dma.c
> - have not NULL-terminated pci_device_id record. This is "easy" to fix, but
> currently I excluding this modules in script. For you I attaching patch for
> this modules and related script ("modulesfix4patched") too.
Thanks, can you format that patch with a simple description and a
Signed-off-by: line and I'll apply it (see Documentation/SubmittingPatches,
especially part 12).
Then can you send me another patch with the results of your script.
Finally, I suggest that your script should only fix files when passed --fix,
and create a config option to run it (without --fix) under in
lib/Kconfig.debug.
Thanks!
Rusty.
next parent reply other threads:[~2010-08-19 0:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C6BE292.3060307@bspu.unibel.by>
2010-08-19 0:50 ` Rusty Russell [this message]
2010-08-19 14:58 ` #3 (Re: More modaliases + patchtool) Dzianis Kahanovich
[not found] ` <4C6D26BC.9040805@bspu.unibel.by>
2010-09-11 2:14 ` #2 " Rusty Russell
2010-09-11 3:36 ` Jeremy Fitzhardinge
2010-09-13 3:03 ` Rusty Russell
2010-09-11 17:51 ` Dmitry Torokhov
2010-09-13 3:24 ` Rusty Russell
2010-09-17 10:55 ` pci: Re: #2 (Re: More modaliases + patchtool)) Dzianis Kahanovich
2010-09-17 13:11 ` Dzianis Kahanovich
2010-09-17 13:26 ` xenbus: " Dzianis Kahanovich
2010-09-17 18:09 ` Jeremy Fitzhardinge
2010-09-17 13:27 ` usb: " Dzianis Kahanovich
2010-09-17 13:29 ` serio: " Dzianis Kahanovich
2010-09-17 13:29 ` pnp: " Dzianis Kahanovich
2010-09-17 13:32 ` of: " Dzianis Kahanovich
2010-09-17 13:35 ` i2c: " Dzianis Kahanovich
2010-09-17 14:06 ` Mark Brown
2010-09-17 15:47 ` Dzianis Kahanovich
2010-09-17 15:54 ` Mark Brown
2010-09-17 13:36 ` hid: " Dzianis Kahanovich
2010-09-17 13:36 ` dio: " Dzianis Kahanovich
2010-09-17 13:37 ` ccw: " Dzianis Kahanovich
2010-09-17 13:38 ` acpi: " Dzianis Kahanovich
2010-09-17 13:38 ` spi " Dzianis Kahanovich
2010-09-17 13:39 ` RapidIO: " Dzianis Kahanovich
2010-09-17 13:42 ` platform: " Dzianis Kahanovich
2010-09-17 13:54 ` Mark Brown
2010-09-17 15:55 ` acpi (signed): " Dzianis Kahanovich
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=201008191020.52861.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mahatma@eu.by \
/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