All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Andrew Melnychenko <andrew@daynix.com>
Cc: qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>
Subject: ebpf/rss.bpf.skeleton.h generated by what?
Date: Fri, 06 May 2022 14:25:59 +0200	[thread overview]
Message-ID: <87a6bulueg.fsf@pond.sub.org> (raw)

ebpf/rss.bpf.skeleton.h contains

    /* THIS FILE IS AUTOGENERATED! */

If it was generated by something in the tree, it should not be committed
to git.  Doesn't look like it is.

Perhaps it was copied from elsewhere, but the commit message offers no
clue.

Please advise.



             reply	other threads:[~2022-05-06 12:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06 12:25 Markus Armbruster [this message]
2022-05-07  5:05 ` ebpf/rss.bpf.skeleton.h generated by what? Jason Wang
2022-05-07  6:46   ` Paolo Bonzini
2022-05-07  6:53     ` Jason Wang
2022-05-07  6:58       ` Paolo Bonzini
2022-05-07  7:08         ` Jason Wang
2022-05-09  5:27           ` Markus Armbruster
2022-05-09  6:52             ` Jason Wang
2022-05-09  8:41             ` Peter Maydell
2022-05-09  9:35               ` Jason Wang
2022-05-10 12:15                 ` Andrew Melnichenko
2022-05-11  8:53                   ` Jason Wang
2022-05-11 12:46                     ` Markus Armbruster

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=87a6bulueg.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=andrew@daynix.com \
    --cc=jasowang@redhat.com \
    --cc=qemu-devel@nongnu.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.