> No, it does matter. Your suggestion doesn't work, because
> /sys/module/scsi_mod/parameters/ belongs to the module code. To create
> a new attribute there, you use the module_param() code -- and there's
> no way to have code called when your parameter is changed.
If I'm not misunderstandin
On Wed, May 16, 2007 at 04:57:52AM +0530, Satyam Sharma wrote:
> [ I appreciate you forked the thread and gave it a better subject name,
> it would be better still if you could maintain the original CC list,
> thanks. ]
I removed the people I didn't think needed to be on the Cc list any more,
sin
On 5/16/07, Arjan van de Ven <[EMAIL PROTECTED]> wrote:
Satyam Sharma wrote:
>> > >semantics of it (read-only? read-write? write-only?
>
> Well, it _has_ to be write, don't really care if it's read-write or
> write-only. I would still prefer read-write, but we can go ahead with
> write-only too
Satyam Sharma wrote:
> >semantics of it (read-only? read-write? write-only?
Well, it _has_ to be write, don't really care if it's read-write or
write-only. I would still prefer read-write, but we can go ahead with
write-only too. It doesn't really matter, does it?
just to be devils advocate
Hi,
[ I appreciate you forked the thread and gave it a better subject name,
it would be better still if you could maintain the original CC list, thanks. ]
On Tue, May 15, 2007 at 12:26:29PM +0100, Simon Arlott wrote:
I've already suggested a sysfs attribute - or something equivalent - would
be
Signed-off-by: Stefan Richter <[EMAIL PROTECTED]>
---
drivers/scsi/Kconfig | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
Index: linux-2.6.22-rc1/drivers/scsi/Kconfig
===
--- linux-2.6.22-rc1.orig/drivers/scs
On Tue, 2007-05-15 at 13:37 -0700, David Miller wrote:
> From: James Bottomley <[EMAIL PROTECTED]>
> Date: Tue, 15 May 2007 12:57:25 -0400
>
> > It might make sense to put it in lib ... however, I don't think many
> > architectures have the problems we have ... specifically certain boxes
> > can h
From: James Bottomley <[EMAIL PROTECTED]>
Date: Tue, 15 May 2007 12:57:25 -0400
> It might make sense to put it in lib ... however, I don't think many
> architectures have the problems we have ... specifically certain boxes
> can have >1 IOMMU, then you really have to know *which* iommu you're
> p
On Tue, May 15, 2007 at 05:30:50PM +0100, Simon Arlott wrote:
> On 15/05/07 13:02, Matthew Wilcox wrote:
> >It's easy to suggest a sysfs attribute. What you've failed to do is
> >suggest the pathname of the sysfs attribute, the contents of it, or the
> >semantics of it (read-only? read-write? wr
On Tue, 2007-05-15 at 12:57 +0100, Christoph Hellwig wrote:
> On Tue, May 15, 2007 at 06:54:16AM -0500, James Bottomley wrote:
> > Er ... I really hope not ... that's exactly how the parisc iommu
> > platform code works ... and why I designed the generic dma mapping this
> > way. The key thing par
On 15/05/07 13:02, Matthew Wilcox wrote:
On Tue, May 15, 2007 at 12:26:29PM +0100, Simon Arlott wrote:
I've already suggested a sysfs attribute - or something equivalent - would
be much better. It's just one function that a user might want to run multiple
times (e.g. after adding scsi devices?)
Hello, Henrique.
Henrique de Moraes Holschuh wrote:
> On Mon, 14 May 2007, Francesco Pretto wrote:
>> Ubuntu [1] ang Gentoo [2] bugs opened. Sent a mail to Miquel van
>> Smoorenburg, dev of sysvinit.
>
> For all Debian sysvinit issues, please send email to
> [EMAIL PROTECTED] (added to CC).
>
>
As discussed in the bugzilla outlined below, we have an sa based
(Mustang) RAID adapter on the system, a Dell PERC2/QC. Affected
controllers are HP NetRAID, Adaptec AAC-364, Dell PERC2/QC or Adaptec
5400S. This problem coincides with the introduction of the adapter_comm
and adapter_deliver platfor
On Tue, May 15, 2007 at 12:26:29PM +0100, Simon Arlott wrote:
> I've already suggested a sysfs attribute - or something equivalent - would
> be much better. It's just one function that a user might want to run multiple
> times (e.g. after adding scsi devices?) - why should loading a module be used
On Tue, May 15, 2007 at 06:54:16AM -0500, James Bottomley wrote:
> Er ... I really hope not ... that's exactly how the parisc iommu
> platform code works ... and why I designed the generic dma mapping this
> way. The key thing parisc needed was the ability to walk up different
> busses until it fo
On Tue, 2007-05-15 at 10:01 +0100, Christoph Hellwig wrote:
> On Mon, May 14, 2007 at 05:39:06PM +0200, Stefan Richter wrote:
> > FUJITA Tomonori wrote:
> > >> > There are two patches for each driver, removing the non-use-sg code
> > >> > and converting to use the accessors.
> > ...
> > > I merged
On Tue, May 15, 2007 01:41, Satyam Sharma wrote:
> On 5/14/07, James Bottomley <[EMAIL PROTECTED]> wrote:
>> On Mon, 2007-05-14 at 17:53 +0530, Satyam Sharma wrote:
>> > > I guess this is probably the behaviour that James wanted originally?
>>
>> No ... you're still not reading the explanation in t
On Mon, May 14, 2007 at 05:39:06PM +0200, Stefan Richter wrote:
> FUJITA Tomonori wrote:
> >> > There are two patches for each driver, removing the non-use-sg code
> >> > and converting to use the accessors.
> ...
> > I merged the two. And I finished cleaning up 35 drivers in total.
> >
> > git://
18 matches
Mail list logo
