mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Oliver Sang <oliver.sang@intel.com>
Cc: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
	lkp@lists.01.org, lkp@intel.com, guobing.chen@intel.com,
	ming.a.chen@intel.com, frank.du@intel.com, Shuhua.Fan@intel.com,
	wangyang.guo@intel.com, Wenhuan.Huang@intel.com,
	jessica.ji@intel.com, shan.kang@intel.com, guangli.li@intel.com,
	tiejun.li@intel.com, yu.ma@intel.com, dapeng1.mi@intel.com,
	jiebin.sun@intel.com, gengxin.xie@intel.com, fan.zhao@intel.com,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [ovl]  30f9ef9479: BUG:kernel_NULL_pointer_dereference,address
Date: Wed, 13 Apr 2022 09:30:12 +0200	[thread overview]
Message-ID: <20220413073012.qwtlopbcbbkffaby@wittgenstein> (raw)
In-Reply-To: <20220411090719.GA21954@xsang-OptiPlex-9020>

On Mon, Apr 11, 2022 at 05:07:19PM +0800, Oliver Sang wrote:
> hi, Christian,
> 
> On Thu, Apr 07, 2022 at 12:26:05PM +0200, Christian Brauner wrote:
> > On Thu, Apr 07, 2022 at 05:40:23PM +0800, kernel test robot wrote:
> > > 
> > > 
> > > Greeting,
> > > 
> > > FYI, we noticed the following commit (built with gcc-11):
> > > 
> > > commit: 30f9ef94795008e5146f69d2eb043922a512bf85 ("ovl: support idmapped layers")
> > > https://github.com/ammarfaizi2/linux-block brauner/linux/fs.idmapped.overlayfs.v3
> > 
> > That's an old branch. :)
> > Anything that has a *.v<idx> appended is basically an old version in my
> > tree. The base branch is always the branch name without the *.v<idx>
> > suffix.
> 
> got it. so there is no need to test these *.v<idx> branches, whatever build,
> boot or function, right? If so, we will disable it.

Yeah, I maintain *.v<idx> branches around. Each time I need to send a
new version of a patchset I do:

git checkout -b base.branch.v<idx> base.branch

and then continue working on

git checkout base.branch

for the new version. :)

I try to make sure to only push base.branch to git.kernel.org once I
know it builds fine. Before that I only push to other code-hosting
platforms. One of the reasons being that I try to avoid upsetting the
various build bots. :)

      reply	other threads:[~2022-04-13  7:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07  9:40 kernel test robot
2022-04-07 10:26 ` Christian Brauner
2022-04-11  9:07   ` Oliver Sang
2022-04-13  7:30     ` Christian Brauner [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=20220413073012.qwtlopbcbbkffaby@wittgenstein \
    --to=brauner@kernel.org \
    --cc=Shuhua.Fan@intel.com \
    --cc=Wenhuan.Huang@intel.com \
    --cc=ammarfaizi2@gnuweeb.org \
    --cc=dapeng1.mi@intel.com \
    --cc=fan.zhao@intel.com \
    --cc=frank.du@intel.com \
    --cc=gengxin.xie@intel.com \
    --cc=guangli.li@intel.com \
    --cc=guobing.chen@intel.com \
    --cc=jessica.ji@intel.com \
    --cc=jiebin.sun@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=ming.a.chen@intel.com \
    --cc=oliver.sang@intel.com \
    --cc=shan.kang@intel.com \
    --cc=tiejun.li@intel.com \
    --cc=wangyang.guo@intel.com \
    --cc=yu.ma@intel.com \
    /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

all inboxes | Powered by JetHome®