All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>, Greg KH <greg@kroah.com>
Subject: Re: virtio: struct device - replace bus_id with dev_name(), dev_set_name()
Date: Thu, 6 Nov 2008 14:45:11 +1100	[thread overview]
Message-ID: <200811061445.12050.rusty@rustcorp.com.au> (raw)
In-Reply-To: <1225393822.21973.39.camel@nga.site>

On Friday 31 October 2008 06:10:22 Kay Sievers wrote:
> This patch is part of a larger patch series which will remove
> the "char bus_id[20]" name string from struct device. The device
> name is managed in the kobject anyway, and without any size
> limitation, and just needlessly copied into "struct device".

OK, I've applied this patch.

I'm curious how you're going to handle out-of-memory conditions?

Thanks,
Rusty.

  reply	other threads:[~2008-11-06  3:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30 19:10 virtio: struct device - replace bus_id with dev_name(), dev_set_name() Kay Sievers
2008-11-06  3:45 ` Rusty Russell [this message]
2008-11-06  6:28   ` Kay Sievers
2008-11-06 11:18     ` Rusty Russell

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=200811061445.12050.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@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 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.