public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

• * FW: Linux-next compilation and build
         [not found] ` <vnymur42hlcdiodh2pyoikdc5646zceiuf6sizgde4jmeqd4xi@b7xt7wuq3aaz>
  @ 2024-12-23 18:20   ` Bondarev, Alex
    2024-12-24  0:19     ` Stephen Rothwell
    0 siblings, 1 reply; 4+ messages in thread
  From: Bondarev, Alex @ 2024-12-23 18:20 UTC (permalink / raw)
    To: linux-next@vger•kernel.org
  
  Forwarding the original message as per the suggestion.
  
  
  On 2024.12.23, 11:39, "Konstantin Ryabitsev" <konstantin@linuxfoundation•org <mailto:konstantin@linuxfoundation•org> <mailto:konstantin@linuxfoundation•org <mailto:konstantin@linuxfoundation•org>>> wrote:
  
  
  
  
  CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
  
  
  
  
  
  
  
  
  
  
  
  
  On Mon, Dec 23, 2024 at 04:16:03PM +0000, Bondarev, Alex wrote:
  > I'm part of a team in AWS that uses the linux-next branch with canonical's
  > ppa to test for build success.
  > git: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
  > ppa: ppa:canonical-kernel-team/ppa
  
  
  
  
  > As a result of this daily test (we try the latest available at time of
  > testing), we have almost immediate knowledge of the "goodness" of the branch
  > (if the machine doesn't boot after update of if the compilation fails). We
  > are currently running build on aarch64 and x86_64 types.
  >
  > The question is should we notify via a mailing list or a single destination
  > about this failure? Will it improve the detection time for a bad merge?
  
  
  
  
  Hello:
  
  
  
  
  The helpdesk isn't quite the right place to answer this question, as I cannot
  speak for the linux-next team. I suggest you send the message to the
  linux-next@vger•kernel.org <mailto:linux-next@vger•kernel.org> <mailto:linux-next@vger•kernel.org <mailto:linux-next@vger•kernel.org>> list (you don't need to subscribe to send mail
  there). They will be able to follow up with suggestions.
  
  
  
  
  Best wishes,
  -K
  
  
  
  
  
  
  
  
  ^ permalink raw reply	[flat|nested] 4+ messages in thread

• • * Re: Linux-next compilation and build
      2024-12-23 18:20   ` FW: Linux-next compilation and build Bondarev, Alex
    @ 2024-12-24  0:19     ` Stephen Rothwell
      2024-12-26 15:29       ` Bondarev, Alex
      0 siblings, 1 reply; 4+ messages in thread
    From: Stephen Rothwell @ 2024-12-24  0:19 UTC (permalink / raw)
      To: Bondarev, Alex; +Cc: linux-next@vger•kernel.org
    
    [-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
    
    Hi Alex,
    
    On Mon, 23 Dec 2024 18:20:50 +0000 "Bondarev, Alex" <alexbnd@amazon•com> wrote:
    >
    > On Mon, Dec 23, 2024 at 04:16:03PM +0000, Bondarev, Alex wrote:
    > > I'm part of a team in AWS that uses the linux-next branch with canonical's
    > > ppa to test for build success.
    > > git: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
    > > ppa: ppa:canonical-kernel-team/ppa  
    > 
    > > As a result of this daily test (we try the latest available at time of
    > > testing), we have almost immediate knowledge of the "goodness" of the branch
    > > (if the machine doesn't boot after update of if the compilation fails). We
    > > are currently running build on aarch64 and x86_64 types.
    > >
    > > The question is should we notify via a mailing list or a single destination
    > > about this failure? Will it improve the detection time for a bad merge? 
    
    Thanks for testing!
    
    Notifications should be sent to linux-next@vger•kernel.org and cc'd to
    linux-kernel@vger•kernel.org and any developers or maintainers that you
    think may be involved with the code causing problems.
     
    -- 
    Cheers,
    Stephen Rothwell
    
    [-- Attachment #2: OpenPGP digital signature --]
    [-- Type: application/pgp-signature, Size: 488 bytes --]
    
    ^ permalink raw reply	[flat|nested] 4+ messages in thread

  • • * Re: Linux-next compilation and build
        2024-12-24  0:19     ` Stephen Rothwell
      @ 2024-12-26 15:29       ` Bondarev, Alex
        2025-01-05  3:34         ` Stephen Rothwell
        0 siblings, 1 reply; 4+ messages in thread
      From: Bondarev, Alex @ 2024-12-26 15:29 UTC (permalink / raw)
        To: Stephen Rothwell; +Cc: linux-next@vger•kernel.org
      
      Sure thing, we'll see how we can automate this.
      Any specific format we should adhere to? (of course we will include the tag that was used and architecture).
      
      On 2024.12.23, 18:19, "Stephen Rothwell" <sfr@canb•auug.org.au <mailto:sfr@canb•auug.org.au>> wrote:
      
      
      Hi Alex,
      
      
      On Mon, 23 Dec 2024 18:20:50 +0000 "Bondarev, Alex" <alexbnd@amazon•com <mailto:alexbnd@amazon•com>> wrote:
      >
      > On Mon, Dec 23, 2024 at 04:16:03PM +0000, Bondarev, Alex wrote:
      > > I'm part of a team in AWS that uses the linux-next branch with canonical's
      > > ppa to test for build success.
      > > git: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
      > > ppa: ppa:canonical-kernel-team/ppa 
      > 
      > > As a result of this daily test (we try the latest available at time of
      > > testing), we have almost immediate knowledge of the "goodness" of the branch
      > > (if the machine doesn't boot after update of if the compilation fails). We
      > > are currently running build on aarch64 and x86_64 types.
      > >
      > > The question is should we notify via a mailing list or a single destination
      > > about this failure? Will it improve the detection time for a bad merge? 
      
      
      Thanks for testing!
      
      
      Notifications should be sent to linux-next@vger•kernel.org <mailto:linux-next@vger•kernel.org> and cc'd to
      linux-kernel@vger•kernel.org <mailto:linux-kernel@vger•kernel.org> and any developers or maintainers that you
      think may be involved with the code causing problems.
      
      
      -- 
      Cheers,
      Stephen Rothwell
      
      
      
      
      ^ permalink raw reply	[flat|nested] 4+ messages in thread

    • • * Re: Linux-next compilation and build
          2024-12-26 15:29       ` Bondarev, Alex
        @ 2025-01-05  3:34         ` Stephen Rothwell
          0 siblings, 0 replies; 4+ messages in thread
        From: Stephen Rothwell @ 2025-01-05  3:34 UTC (permalink / raw)
          To: Bondarev, Alex; +Cc: linux-next@vger•kernel.org
        
        [-- Attachment #1: Type: text/plain, Size: 354 bytes --]
        
        Hi Alex,
        
        On Thu, 26 Dec 2024 15:29:48 +0000 "Bondarev, Alex" <alexbnd@amazon•com> wrote:
        >
        > Sure thing, we'll see how we can automate this.
        > Any specific format we should adhere to? (of course we will include the tag that was used and architecture).
        
        Nothing specific.  Just try to CC the appropriate people.
        
        -- 
        Cheers,
        Stephen Rothwell
        
        [-- Attachment #2: OpenPGP digital signature --]
        [-- Type: application/pgp-signature, Size: 488 bytes --]
        
        ^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2025-01-05  3:42 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <4FF05C5D-F7C0-4212-9917-0D94DF3DCA60@contoso.com>
     [not found] ` <vnymur42hlcdiodh2pyoikdc5646zceiuf6sizgde4jmeqd4xi@b7xt7wuq3aaz>
2024-12-23 18:20   ` FW: Linux-next compilation and build Bondarev, Alex
2024-12-24  0:19     ` Stephen Rothwell
2024-12-26 15:29       ` Bondarev, Alex
2025-01-05  3:34         ` Stephen Rothwell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox