All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <groeck@google.com>
To: kbuild-all@lists.01.org
Subject: Re: Fwd: [PATCH] objtool, perf: fix stream_open.cocci warnings
Date: Mon, 13 Jan 2020 15:27:18 -0800	[thread overview]
Message-ID: <CABXOdTfd+UA6wMk-vwOc4n5T7CHBpUSTpHnDJ6bCftB+6-=EpA@mail.gmail.com> (raw)
In-Reply-To: <831EE4E5E37DCC428EB295A351E6624952319A55@shsmsx102.ccr.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1933 bytes --]

On Mon, Jan 13, 2020 at 3:18 PM Li, Philip <philip.li@intel.com> wrote:
>
> > Subject: Re: [kbuild-all] Re: Fwd: [PATCH] objtool, perf: fix stream_open.cocci
> > warnings
> >
> > Hi Philip,
> >
> > On Mon, Jan 13, 2020 at 3:08 PM Li, Philip <philip.li@intel.com> wrote:
> > >
> > > > On Mon, Jan 13, 2020 at 10:52 AM Kirill Smelkov <kirr@nexedi.com> wrote:
> > > > >
> > > > > On Mon, Jan 13, 2020 at 10:32:53AM -0800, Todd Kjos wrote:
> > > > > > > tree:   https://android.googlesource.com/kernel/common android-4.9-o-
> > mr1
> > > > > >
> > > > > > Looks like the comment was related to an issue found on the
> > > > > > android-4.9-o-mr1 branch which doesn't get LTS merges and is really
> > > > > > just a patch repository for patches cited in the Android Security
> > > > > > Bulletin. We don't do general bug-fixes or take LTS merges on that
> > > > > > branch.
> > > > >
> > > > > Greg, Todd, thanks for feedback. Indeed, it was about android-4.9-o-mr1,
> > > > > which I mistakenly attributed to only android-4.9-o . Good to hear that
> > > > > main Android branches are in a good shape.
> > > > >
> > > > > Julia, if I understand correctly, it seems it is better to remove -mrX
> > > > > branches from being tracked by kbuild robot as that is causing
> > > > > confusion to people.
> > > >
> > > > Yes, remove "-mr1" and "-release" branches.
> > > Got it, we will blacklist these branches -mrX and -release in the bot.
> > >
> >
> > Since you are at it, would it be possible to add chromeos-5.4 to the
> > list of tested branches ? I sent a pull request at github a few of
> > weeks ago, but it doesn't look like those are handled.
> Sure, I will add it very soon.
>
> BTW: the official repo is at https://github.com/intel/lkp-tests, probably
> your request goes to fengguang's original one.
>

Ah yes, of course. Thanks a lot for the pointer, and for adding the branch.

Guenter

  reply	other threads:[~2020-01-13 23:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.2.21.2001131717230.4078@hadrien>
2020-01-13 18:04 ` Fwd: [PATCH] objtool, perf: fix stream_open.cocci warnings Kirill Smelkov
2020-01-13 18:21   ` Greg Kroah-Hartman
2020-01-13 18:32     ` Todd Kjos
2020-01-13 18:52       ` Kirill Smelkov
2020-01-13 18:56         ` Todd Kjos
2020-01-13 23:08           ` Li, Philip
2020-01-13 23:15             ` Guenter Roeck
2020-01-13 23:18               ` Li, Philip
2020-01-13 23:27                 ` Guenter Roeck [this message]
2020-01-13 21:48         ` Julia Lawall

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='CABXOdTfd+UA6wMk-vwOc4n5T7CHBpUSTpHnDJ6bCftB+6-=EpA@mail.gmail.com' \
    --to=groeck@google.com \
    --cc=kbuild-all@lists.01.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.