From: Christoph Fritz <chf.fritz@googlemail.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] commands: add 'findstr' to get string from file
Date: Tue, 20 May 2014 22:29:20 +0200 [thread overview]
Message-ID: <1400617760.26128.270.camel@mars> (raw)
In-Reply-To: <20140520180830.GA4321@omega>
Hi Alexander
On Tue, 2014-05-20 at 20:08 +0200, Alexander Aring wrote:
> On Tue, May 20, 2014 at 07:27:55PM +0200, Christoph Fritz wrote:
> > +config CMD_FINDSTR
> > + tristate
> > + default n
> not needed.
Ok
> > + while ((opt = getopt(argc, argv, "o:l:t:")) > 0) {
> > + switch (opt) {
> > + case 'o':
> > + offset = simple_strtoul(optarg, NULL, 0);
> > + break;
> > + case 'l':
> > + len = simple_strtoul(optarg, NULL, 0);
> > + break;
> > + case 't':
> > + t = optarg;
> > + break;
> > + }
>
> switch case without default branch can occur compiler warnings.
>
> You should return COMMAND_ERROR_USAGE in the default branch if non valid
> parameter is given.
Ok
> > + fd = open(argv[optind+1], O_RDONLY);
> > + if (fd < 0)
> > + return COMMAND_ERROR_USAGE;
> > +
> > + while (1) {
> > + r = read(fd, mem_rw_buf, RW_BUF_SIZE);
> > + if (r < 0) {
> > + ret = -EIO;
> > + goto out;
> > + }
> > + if (!r)
> > + break;
> > +
> > + v_idx = 0;
> > +
> > + while (r) {
> > + if (v[v_idx] == s[s_idx])
> > + s_idx++;
> > + else
> > + s_idx = 0;
> > +
> > + idx++;
> > + v_idx++;
> > +
> > + if (s_idx == strlen(s)) { /* found */
> > + loff_t sz;
> > + loff_t hit = idx - strlen(s);
> > +
> > + if (lseek(fd, hit + offset, SEEK_SET) < 0) {
> > + ret = -EIO;
> > + goto out;
> > + }
> > +
> > + if (!len)
> > + len = strlen(s);
> > + sz = min_t(loff_t, len, RW_BUF_SIZE - 1);
> > + r = read(fd, mem_rw_buf, sz);
> > + if (r != sz) {
> > + ret = -EIO;
> > + goto out;
> > + }
> > +
> > + v[sz] = '\0';
> > +
> > + if (t)
> > + setenv(t, v);
> > + else
> > + printf("%s\n", v);
> > +
> > + ret = 0;
> > + goto out;
> > + }
> > + r--;
> > + }
>
> Why not use read_file and the awesome string function strstr and then
> write the file back.
read_file() reads the whole file which can get pretty slow over an i2c
link accessing an eeprom which mostly holds the configuration-string at
the beginning.
Why would I want to write the file back?
Thanks
-- Christoph
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-05-20 20:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 17:27 [PATCH] commands: add 'findstr' to get string from file Christoph Fritz
2014-05-20 18:08 ` Alexander Aring
2014-05-20 20:29 ` Christoph Fritz [this message]
2014-05-21 3:44 ` Alexander Aring
2014-05-21 8:02 ` [PATCH v2] commands: add 'findstr' to search file for string Christoph Fritz
2014-05-21 9:22 ` Antony Pavlov
2014-05-21 9:49 ` Christoph Fritz
2014-05-21 13:51 ` [PATCH] commands: add 'findstr' to get string from file Sascha Hauer
2014-05-22 9:20 ` Christoph Fritz
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=1400617760.26128.270.camel@mars \
--to=chf.fritz@googlemail.com \
--cc=alex.aring@gmail.com \
--cc=barebox@lists.infradead.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.