linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Schoenebeck <linux_oss@crudebyte.com>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the v9fs tree
Date: Thu, 08 Dec 2022 16:55:17 +0100	[thread overview]
Message-ID: <6054083.7yRespAWZ4@silver> (raw)
In-Reply-To: <Y45zsz71RfXbySDq@codewreck.org>

On Monday, December 5, 2022 11:41:55 PM CET Dominique Martinet wrote:
> Christian Schoenebeck wrote on Mon, Dec 05, 2022 at 09:40:06PM +0100:
> > Dominique, looking at your 9p queue, I just realized what happened here: I 
> > posted a v2 of these two patches, which got lost for some reason:
> > 
> > https://lore.kernel.org/all/cover.1669144861.git.linux_oss@crudebyte.com/
> > 
> > The currently queued 1st patch is still v1 as well.
> 
> Oh. Now how did I manage that one..
> Thanks for the catch, and v2 had the valid printf modifier...

You remember updating the 1st patch as well, right? :)

In general, I'm sure nobody complains about extra noise like "queued on...".
Then it's also more likely for other people to get which patches are still
pending or unseen.




  reply	other threads:[~2022-12-08 15:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-05  4:03 linux-next: build failure after merge of the v9fs tree Stephen Rothwell
2022-12-05  4:10 ` Dominique Martinet
2022-12-05  4:55   ` Stephen Rothwell
2022-12-05 14:31   ` Christian Schoenebeck
2022-12-05 20:40     ` Christian Schoenebeck
2022-12-05 22:41       ` Dominique Martinet
2022-12-08 15:55         ` Christian Schoenebeck [this message]
2022-12-08 23:53           ` Dominique Martinet
2022-12-09 14:40             ` Christian Schoenebeck
2022-12-09 21:24               ` Dominique Martinet
  -- strict thread matches above, loose matches on Subject: below --
2022-07-13  1:02 Stephen Rothwell
2022-07-13  1:06 ` Dominique Martinet
2011-12-01  1:02 Stephen Rothwell
2011-12-01 16:57 ` Joe Perches
2011-02-22  0:53 Stephen Rothwell
2011-02-22  5:20 ` Venkateswararao Jujjuri (JV)
2011-02-22  5:30   ` Stephen Rothwell
2011-02-22  6:22     ` Venkateswararao Jujjuri (JV)
2011-02-22 14:57       ` Eric Van Hensbergen
2011-02-22 16:48         ` Venkateswararao Jujjuri (JV)

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=6054083.7yRespAWZ4@silver \
    --to=linux_oss@crudebyte.com \
    --cc=asmadeus@codewreck.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).