From: Matt Tolentino <metolent@snoqualmie.dp.intel.com>
To: akpm@osdl.org, alex.williamson@hp.com, Matt_Domsch@dell.com
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/3] efivars driver update and move
Date: Fri, 30 Apr 2004 00:09:10 +0000 [thread overview]
Message-ID: <200404300155.i3U1tEs3004947@snoqualmie.dp.intel.com> (raw)
In-Reply-To: <200404221732.i3MHWJcc023373@snoqualmie.dp.intel.com>
> On Thu, 2004-04-29 at 15:19, Matt Domsch wrote:
> > On Thu, Apr 29, 2004 at 01:50:54PM -0600, Alex Williamson wrote:
> > > # stat BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c\ /
> > > File: `BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c /'
> >
> > FWIW, my Intel Tiger2-based system doesn't have the space
> at the end...
> >
> > > *(short_name + strlen(short_name)) = '-';
> > > efi_guid_unparse(vendor_guid, short_name +
> strlen(short_name));
> > > *(short_name + strlen(short_name)) = ' ';
> >
> > even though looking at this I would have expected it to...
>
> Yeah, I'm not sure how you couldn't have a space at the end...
That's odd.
> > Can you remove that last line and see what it does? Best as I can
> > tell, it isn't necessary or desired.
>
> Yes, removing that last line above gets rid of the space,
> everything
> looks right, and efibootmgr doesn't complain. I'd attach a patch but
> I'm curious if Matt T. had some reason for adding it.
I had it in there because when I originally rewrote this
driver for sysfs it kept cutting off the last character. I
had to put it aside for a bit and just didn't take it out
last week before I resent it. I just retried it on local
ia64 and x86 machines and it worked fine on both accounts
without the extra space.
Andrew, can you please apply the following patch to remove
space?
thanks,
matt
diff -urN linux-2.6.6-rc3-clean/drivers/firmware/efivars.c linux-2.6.6-rc3/drivers/firmware/efivars.c
--- linux-2.6.6-rc3-clean/drivers/firmware/efivars.c 2004-04-27 18:36:33.000000000 -0700
+++ linux-2.6.6-rc3/drivers/firmware/efivars.c 2004-04-29 16:31:48.052355632 -0700
@@ -633,7 +633,6 @@
*(short_name + strlen(short_name)) = '-';
efi_guid_unparse(vendor_guid, short_name + strlen(short_name));
- *(short_name + strlen(short_name)) = ' ';
kobject_set_name(&new_efivar->kobj, short_name);
kobj_set_kset_s(new_efivar, vars_subsys);
prev parent reply other threads:[~2004-04-30 0:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 15:51 [patch 1/3] efivars driver update and move Matt Tolentino
2004-04-22 16:46 ` Bjorn Helgaas
2004-04-22 17:14 ` Tolentino, Matthew E
2004-04-22 17:20 ` Bjorn Helgaas
2004-04-29 19:50 ` Alex Williamson
2004-04-29 21:19 ` Matt Domsch
2004-04-29 22:08 ` Alex Williamson
2004-04-23 22:29 ` Matt Domsch
2004-04-24 3:41 ` Matt Domsch
2004-04-26 18:57 ` Matt Domsch
2004-04-26 19:30 ` Matt Tolentino
2004-04-30 0:09 ` Matt Tolentino [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=200404300155.i3U1tEs3004947@snoqualmie.dp.intel.com \
--to=metolent@snoqualmie.dp.intel.com \
--cc=Matt_Domsch@dell.com \
--cc=akpm@osdl.org \
--cc=alex.williamson@hp.com \
--cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox