All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/4] lib: Add support for linux stable and glibc tags
Date: Tue, 23 Feb 2021 12:30:03 +0100	[thread overview]
Message-ID: <YDTnO83+enCs5Wdn@pevik> (raw)
In-Reply-To: <YDTNtBH/9mz4I2OL@yuki.lan>

Hi Cyril,

> Hi!
> >  #define LINUX_GIT_URL "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id="
> > +#define LINUX_STABLE_GIT_URL "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id="
> > +#define GLIBC_GIT_URL "https://sourceware.org/git/?p=glibc.git;a=commit;h="
> >  #define CVE_DB_URL "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-"

> >  struct tst_test *tst_test;
> > @@ -492,6 +495,8 @@ static void print_test_tags(void)
> >  			printf(CVE_DB_URL "%s\n", tags[i].value);
> >  		else if (!strcmp(tags[i].name, "linux-git"))
> >  			printf(LINUX_GIT_URL "%s\n", tags[i].value);
> > +		else if (!strcmp(tags[i].name, "linux-stable-git"))
> > +			printf(LINUX_STABLE_GIT_URL "%s\n", tags[i].value);

> Shouldn't we add GLIBC_GIT_URL handling here as well?
+1 thanks.

> The rest looks good.
Thanks! (counting your Reviewed-by: tag for this commit).

Kind regards,
Petr

  reply	other threads:[~2021-02-23 11:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 16:02 [LTP] [PATCH 0/4] Support for linux stable and glibc tags Petr Vorel
2021-02-22 16:02 ` [LTP] [PATCH 1/4] lib: Add support " Petr Vorel
2021-02-23  9:41   ` Cyril Hrubis
2021-02-23 11:30     ` Petr Vorel [this message]
2021-02-22 16:02 ` [LTP] [PATCH 2/4] testinfo.pl: Update parsing more git trees Petr Vorel
2021-03-10 15:51   ` Cyril Hrubis
2021-02-22 16:02 ` [LTP] [PATCH 3/4] io_uring02: Add linux-stable-git tag Petr Vorel
2021-03-10 15:52   ` Cyril Hrubis
2021-02-22 16:02 ` [LTP] [PATCH 4/4] semctl09: Add glibc-git tag Petr Vorel
2021-03-10 15:53   ` Cyril Hrubis
2021-03-10 17:07     ` Petr Vorel

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=YDTnO83+enCs5Wdn@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    /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.